How to Use the Eventcube MCP in LlamaIndex

Q: How do I load Eventcube tools into LlamaIndex?

Install llama-index-tools-mcp and instantiate BasicMCPClient. Wrap it with McpToolSpec and call totoollistasync() to expose the Eventcube endpoints to your RAG application.

Q: Can LlamaIndex cache Eventcube API responses?

Yes. You can index the output of listevents into your vector store. The agent will query the local index first, saving API calls and reducing latency for common questions.

Q: How do I restrict which MCP tools LlamaIndex can use?

Use the allowedtools filter when setting up your McpToolSpec. You can expose read-only tools like getevent while blocking potentially destructive actions like createevent.

Q: Is Eventcube customer data secure in LlamaIndex?

Tools like listorders process names, physical addresses, and ticket quantities. LlamaIndex keeps this information confined to your local vector store, ensuring no third-party services scrape your attendee lists during semantic searches.

Index live Eventcube ticketing data into searchable vector stores using LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Eventcube MCP to LlamaIndex

Create your Vinkius account to connect Eventcube 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 Eventcube with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index live ticketing catalogs

The `list_events` and `list_venues` tools feed directly into your LlamaIndex vector stores. Your agent pulls the entire upcoming event schedule and embeds it alongside your static marketing PDFs. Users can query the index in plain English. Instead of guessing API parameters, the agent searches the vector database to find which events are happening at specific venues this weekend.

Search Eventcube MCP Server orders

You can build RAG applications that index historical purchase data using `list_orders`. When a support rep asks about a specific buyer, the agent retrieves the exact `get_order` payload from the index. This eliminates API hallucination. The LLM bases its answers strictly on the actual JSON returned by the Eventcube tools, ensuring you never give a customer incorrect refund or ticket status information.

Ground your AI in real inventory

Run `list_categories` and `list_tickets` to build a semantic map of your pricing tiers. The LlamaIndex agent understands the difference between VIP and General Admission because it read the actual definitions from your account. You pass these tools to a `FunctionAgent` to handle complex queries. If the index lacks the current ticket count, the agent dynamically calls the API to fetch the missing context before answering.

Setup guide

Set up Eventcube 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 Eventcube 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 Eventcube tools.",
)
response = await agent.run("List recent Eventcube 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 Eventcube. 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 Eventcube 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 Eventcube MCP in LlamaIndex

Install `llama-index-tools-mcp` and instantiate `BasicMCPClient`. Wrap it with `McpToolSpec` and call `to_tool_list_async()` to expose the Eventcube endpoints to your RAG application.

Yes. You can index the output of `list_events` into your vector store. The agent will query the local index first, saving API calls and reducing latency for common questions.

Your agent will fall back to the last indexed data. You can configure a tool like `get_me` to verify connectivity before attempting to execute write operations like `create_ticket`.

Use the `allowed_tools` filter when setting up your `McpToolSpec`. You can expose read-only tools like `get_event` while blocking potentially destructive actions like `create_event`.

Tools like `list_orders` process names, physical addresses, and ticket quantities. LlamaIndex keeps this information confined to your local vector store, ensuring no third-party services scrape your attendee lists during semantic searches.

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