How to Use the Eventmaker MCP in LlamaIndex

Q: How do I configure Eventmaker with LlamaIndex?

Install llama-index-tools-mcp. Create a BasicMCPClient with your endpoint URL, wrap it in an McpToolSpec, and call totoollistasync(). Pass those tools directly to your FunctionAgent.

Q: Can LlamaIndex filter which Eventmaker MCP tools the agent uses?

Yes. You pass an allowedtools array when initializing the tool spec. If you only want the agent to read schedules, you restrict it to geteventdetaileddata and listeventsessions.

Q: Does LlamaIndex index the Eventmaker check-in logs automatically?

Not by default. Your agent must explicitly call quickeventengagementaudit or the check-in tools. LlamaIndex then takes that JSON output, chunks it, and adds it to your vector store for semantic search.

Q: How do I analyze event performance over time?

Your agent calls geteventperformancestats periodically. It embeds these snapshots into your index. You then prompt your RAG application to compare last week's registration velocity against today's numbers.

Index Eventmaker data into LlamaIndex. Build RAG applications that query live participant logs and event schedules.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Eventmaker MCP to LlamaIndex

Create your Vinkius account to connect Eventmaker to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Eventmaker with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Connect the Eventmaker MCP Server

The Eventmaker MCP Server turns your event data into a dynamic knowledge base. LlamaIndex ingests live API responses directly into your vector store. You aren't just calling endpoints. You are building a searchable index. The agent pulls the schedule using `list_event_sessions` and embeds the descriptions. When a user asks about afternoon keynotes, the system retrieves the exact session details from the index without hallucinating times or locations.

Ground queries in real event data

This MCP Server lets you stop guessing about event capacity and start querying facts. The agent pulls metadata via `get_eventmaker_account_metadata` to understand account limits before provisioning new events. It then runs `list_all_events` to map out the current calendar. Your RAG setup cross-references this live snapshot against your historical documents. This gives you a complete picture of your event pipeline.

Index exhibitors and check-ins

The Eventmaker MCP tool grabs the partner manifest using `list_event_exhibitors` and stores it. Sponsor management requires accurate traffic data. It then tracks floor movement by pulling `list_event_checkins_log`. You query the index to find out which sponsors saw the most foot traffic. The agent correlates the check-in timestamps with booth locations, returning precise answers based entirely on actual scan records.

Setup guide

Set up Eventmaker MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Eventmaker MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Eventmaker tools.",
)
response = await agent.run("List recent Eventmaker data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Eventmaker. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Eventmaker now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Eventmaker MCP in LlamaIndex

Install `llama-index-tools-mcp`. Create a `BasicMCPClient` with your endpoint URL, wrap it in an `McpToolSpec`, and call `to_tool_list_async()`. Pass those tools directly to your `FunctionAgent`.

Yes. You pass an `allowed_tools` array when initializing the tool spec. If you only want the agent to read schedules, you restrict it to `get_event_detailed_data` and `list_event_sessions`.

Not by default. Your agent must explicitly call `quick_event_engagement_audit` or the check-in tools. LlamaIndex then takes that JSON output, chunks it, and adds it to your vector store for semantic search.

Your agent calls `get_event_performance_stats` periodically. It embeds these snapshots into your index. You then prompt your RAG application to compare last week's registration velocity against today's numbers.

When your LlamaIndex application fetches sponsor emails and phone numbers, the request routes through Vinkius's isolated infrastructure. The V8 sandbox authenticates the endpoint token, executes the API call, and immediately terminates. No customer records ever touch a persistent disk.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript