How to Use the Line-Up MCP in LlamaIndex

Q: How do I index Line-Up event details using LlamaIndex?

You fetch the event data via geteventdetails and wrap the output in a LlamaIndex Document object. This document is then ingested into your vector store, making the show details instantly searchable.

Q: Can LlamaIndex query live ticket availability in Line-Up?

Yes, the agent calls checkticketavailability dynamically during the query phase to get real-time seat counts. It combines this live data with your indexed event information to answer availability questions accurately.

Q: How do LlamaIndex search indexes update when Line-Up performances change?

You run a sync task that calls listeventperformances using the MCP Server and updates the corresponding vector embeddings. This ensures your semantic search queries always reflect the latest schedule.

Q: Can I use agentic RAG to handle the checkout process?

Yes, you can equip a LlamaIndex FunctionAgent with createticketreservation and confirmticketorder. The agent queries its vector store for event IDs and then executes the booking steps in order.

Q: How are customer profiles protected when indexing Line-Up data?

Data fetched via listticketcustomers is processed in memory and only indexed locally in your private vector store. Vinkius executes the underlying MCP Server in an ephemeral sandbox, leaving no trace of customer records behind.

Build data-grounded event booking applications using LlamaIndex and this Line-Up MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Line-Up MCP to LlamaIndex

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Index active event inventories into LlamaIndex vector stores

`list_available_events` pulls raw event data directly into your LlamaIndex documents for immediate semantic indexing. Your agent queries this local index to answer user questions about upcoming shows without hitting the live API repeatedly.

Query transaction histories using semantic search

`list_account_orders` extracts historical purchase logs and indexes them into your local vector database. When a user asks about their past purchases, LlamaIndex searches this index instead of making expensive API calls.

Build a RAG-driven booking engine with this MCP Server

`check_ticket_availability` provides the live inventory metrics that ground your agent's booking decisions. LlamaIndex uses this real-time data to verify seat counts before executing `create_ticket_reservation`.

Setup guide

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

You fetch the event data via `get_event_details` and wrap the output in a LlamaIndex Document object. This document is then ingested into your vector store, making the show details instantly searchable.

Yes, the agent calls `check_ticket_availability` dynamically during the query phase to get real-time seat counts. It combines this live data with your indexed event information to answer availability questions accurately.

You run a sync task that calls `list_event_performances` using the MCP Server and updates the corresponding vector embeddings. This ensures your semantic search queries always reflect the latest schedule.

Yes, you can equip a LlamaIndex FunctionAgent with `create_ticket_reservation` and `confirm_ticket_order`. The agent queries its vector store for event IDs and then executes the booking steps in order.

Data fetched via `list_ticket_customers` is processed in memory and only indexed locally in your private vector store. Vinkius executes the underlying MCP Server in an ephemeral sandbox, leaving no trace of customer records behind.

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