Bring Mobile Apps
to LlamaIndex
Learn how to connect Guidebook to LlamaIndex 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 LlamaIndex?
LlamaIndex agents combine Guidebook tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine Guidebook tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain Guidebook tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query Guidebook, a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what Guidebook tools were called, what data was returned, and how it influenced the final answer
Guidebook in LlamaIndex
Guidebook and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Guidebook to LlamaIndex 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 LlamaIndex
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 LlamaIndex 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 LlamaIndex
Every tool call from LlamaIndex 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 LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query Guidebook tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp