Bring Mobile Apps
to Pydantic AI
Learn how to connect Guidebook to Pydantic AI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Guidebook MCP Server?
Connect your Guidebook Builder account to any AI agent and take full control of your mobile event guides and scheduling workflows through natural conversation.
What you can do
- Guide Orchestration — List and manage all mobile guides in your account and retrieve detailed guide metadata
- Schedule Management — Access and monitor event schedules and sessions programmatically to keep your attendees updated
- Location Mapping — List and search for mapped event locations to ensure precise spatial coordination for your attendees
- Custom Lists — Manage and retrieve custom lists (speakers, exhibitors, sponsors) to organize your event's intellectual capital
- Activity Monitoring — Check guide details and status directly through your agent for instant event reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from the Guidebook Builder (Manage your account > API Key)
3. Start managing your mobile guides from Claude, Cursor, or any MCP client
No more manual editing of sessions or locations through complex web builders. Your AI acts as your dedicated event mobile coordinator.
Who is this for?
- Event Organizers — scale mobile guide management and session coordination for large-scale conferences
- Marketing Teams — update exhibitor and sponsor lists across multiple guides through natural language queries
- Onboarding Leads — keep employees updated on company training schedules and locations without leaving your workspace
Built-in capabilities (12)
Verify connectivity
Add list item
Create a guide
Get session details
Get guide details
List attendees
List custom list items
List custom lists
List sessions
List guides
List locations
Update a guide
Why Pydantic AI?
Pydantic AI validates every Guidebook tool response against typed schemas, catching data inconsistencies at build time. Connect 12 tools through Vinkius and switch between OpenAI, Anthropic, or Gemini without changing your integration code. full type safety, structured output guarantees, and dependency injection for testable agents.
- —
Full type safety: every MCP tool response is validated against Pydantic models, catching data inconsistencies before they reach your application
- —
Model-agnostic architecture. switch between OpenAI, Anthropic, or Gemini without changing your Guidebook integration code
- —
Structured output guarantee: Pydantic AI ensures tool results conform to defined schemas, eliminating runtime type errors
- —
Dependency injection system cleanly separates your Guidebook connection logic from agent behavior for testable, maintainable code
Guidebook in Pydantic AI
Guidebook and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Guidebook to Pydantic AI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Guidebook in Pydantic AI
The Guidebook MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Pydantic AI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Guidebook for Pydantic AI
Every tool call from Pydantic AI to the Guidebook MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find a Guide ID?
You can use the list_guides tool to retrieve all mobile guides in your account along with their unique identifiers and names.
Can I see the speakers or exhibitors for an event?
Yes! Use the list_custom_lists tool with a specific guide_id to retrieve all custom directories like speakers, exhibitors, or sponsors.
Does the integration support viewing the event map?
The list_guide_locations tool provides the metadata for all mapped locations within a guide, helping you identify precisely where sessions take place.
How does Pydantic AI discover MCP tools?
Create an MCPServerHTTP instance with the server URL. Pydantic AI connects, discovers all tools, and generates typed Python interfaces automatically.
Does Pydantic AI validate MCP tool responses?
Yes. When you define result types as Pydantic models, every tool response is validated against the schema. Invalid data raises a clear error instead of silently corrupting your pipeline.
Can I switch LLM providers without changing MCP code?
Absolutely. Pydantic AI abstracts the model layer. your Guidebook MCP integration works identically with OpenAI, Anthropic, Google, or any supported provider.
MCPServerHTTP not found
Update: pip install --upgrade pydantic-ai