This server lets you discover events and compare live ticket listings, all-in prices, and seat maps across multiple marketplaces via read-only tools.
Find upcoming events by name, performer, venue, or marketplace URL, with cross-marketplace event links (free).
Get live listings for one event page, including section, row, seats, sellable quantities, face/fee/all-in prices, cheapest first.
Compare cheapest tickets for a quantity across up to 15 marketplaces by all-in price.
Retrieve section and seat maps (SVG), cheapest all-in price per section, and venue capacity where available.
List supported marketplaces and their host routing (free).
Tools are read-only; they cannot buy, hold, or list tickets. Each marketplace capture is billed except for free tools.
Retrieves live SeatGeek event listings, all-in prices, and seat maps through the Tickets.dev API, enabling price comparison and event lookup across marketplaces.
Retrieves live StubHub event listings, all-in prices, and seat maps through the Tickets.dev API, enabling price comparison and event lookup across marketplaces.
Retrieves live Ticketmaster event listings, all-in prices, and seat maps through the Tickets.dev API, enabling price comparison and event lookup across marketplaces.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@tickets-dev-mcp find the cheapest 2 seats for the Eagles at Sphere and compare prices"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This repo is the home for using Tickets.dev with AI agents. Tickets.dev returns live ticket listings, all-in prices and seat maps from Ticketmaster, StubHub, SeatGeek, Vivid Seats, TickPick, Gametime, Viagogo and more, in one schema.
Tickets.dev is a standard HTTP API, so any agent that can make web requests can use it. This repo adds an agent skill, plugins for popular agent tools, and how to connect the hosted MCP server.
I have 2 seats in section 110, row 36 for the Eagles at Sphere. What are the same and nearby seats listed for on each marketplace?
Show the seat map for this StubHub event with the cheapest all-in price in each section.
How many tickets are listed for each Sphere show next month, and what's the get-in price?
Write a script that saves the listed tickets and get-in price for these events every morning.
Related MCP server: PredMCP
Give your agent the OpenAPI spec, the agent docs and your API key. Get a key at tickets.dev and send it in the x-api-key header.
Most tasks take two calls. Find the event, then capture one marketplace page:
curl "https://api.tickets.dev/v1/events?query=eagles%20sphere" \
-H "x-api-key: $TICKETS_DEV_KEY"
curl -G "https://api.tickets.dev/v1/capture" \
--data-urlencode "url=https://www.ticketmaster.com/eagles-live-at-sphere-las-vegas-nevada-12-11-2026/event/17006483D6FAFC60" \
-H "x-api-key: $TICKETS_DEV_KEY"The tickets-dev skill covers the details of ticket data that agents tend to get wrong, such as all-in prices, sellable quantities, and why a listing that disappears isn't proof of a sale. It's plain Markdown, so you can add it to any agent's instructions.
If you use one of these agent tools, we recommend installing the Tickets.dev plugin. It includes the skill and tools your agent can call directly. The first time the tools are used, you sign in at tickets.dev and approve the connection, so there's no API key to copy.
Run these commands in Claude Code:
/plugin marketplace add Tickets-dot-dev/ai
/plugin install tickets-dev@tickets-devThen run /mcp, pick tickets-dev and choose Authenticate to sign in.
Run this command:
codex plugin marketplace add Tickets-dot-dev/aiThen restart Codex, install Tickets.dev from the Plugins directory, and sign in:
codex mcp login tickets-devInstall the plugin from cursor.directory, or use the MCP server.
Run this command:
gemini extensions install https://github.com/Tickets-dot-dev/aiThen run /mcp auth tickets-dev in Gemini CLI to sign in.
The plugin is coming to the Grok Build marketplace. Until then, use the MCP server.
The tools are hosted at https://api.tickets.dev/mcp (Streamable HTTP).
Add that URL and sign in. You'll be sent to Tickets.dev to sign in and approve the connection, which creates an API key for that app. Disconnect it any time from your account settings.
In Claude Code:
claude mcp add --transport http tickets-dev https://api.tickets.dev/mcpThen run /mcp, pick tickets-dev and choose Authenticate.
In Claude or ChatGPT, add it as a custom connector with the same URL.
In clients that take a URL, for example .cursor/mcp.json:
{
"mcpServers": {
"tickets-dev": {
"url": "https://api.tickets.dev/mcp"
}
}
}For scripts and clients that can't sign in, send an API key as a header instead, for example "headers": { "Authorization": "Bearer tk_live_..." }, or in Claude Code --header "Authorization: Bearer $TICKETS_DEV_KEY".
Clients that only start local servers, such as Claude Desktop's claude_desktop_config.json, can run the tickets-dev-mcp package. It's a small bridge that forwards to the same hosted server:
{
"mcpServers": {
"tickets-dev": {
"command": "npx",
"args": ["-y", "tickets-dev-mcp"],
"env": { "TICKETS_DEV_KEY": "tk_live_..." }
}
}
}Tool | What it does |
| Finds upcoming events and their URL on every marketplace. Free. |
| Returns every listing on one event page, with all-in prices. |
| Ranks one event's listings across marketplaces by all-in price. |
| Returns the section and seat maps, the cheapest price per section and, where the map gives it, venue capacity. |
| Lists supported marketplaces. Free. |
The tools only read data. They can't buy, hold or list tickets.
You only need a key for the HTTP API, scripts, and clients that can't sign in. The tickets-dev-mcp package and the skill's direct API calls read it from the TICKETS_DEV_KEY environment variable:
export TICKETS_DEV_KEY=tk_live_...Restart your agent after setting it. Don't paste your key into a chat. If the key is missing, the agent tells you how to add it.
Each capture of one event on one marketplace is billed, the same as a direct API call. One tool call uses at most 15 captures, and up to 3 tool calls can run at once per account. See pricing.
Guides: compare ticket prices across marketplaces, price and inventory alerts
Examples: price comparison app, price alerts, price tracker
npm install
node --test # offline tests
TICKETS_DEV_E2E_KEY=<your key> node --test # end-to-end through api.tickets.dev/mcp (uses a few captures)MIT. Not affiliated with any ticket marketplace.
Find one event, capture it on each marketplace, and rank the cheapest tickets for a quantity by all-in price (fees included). Each marketplace captured is one billed Tickets.dev capture. Captures up to max_marketplaces (default 7).
Inputs: event (required), top, quantity, max_marketplaces.
Find upcoming events by name, performer, venue or any marketplace event URL, with the same event's URL on every marketplace that lists it (Ticketmaster, StubHub, SeatGeek, Vivid Seats, TickPick, Gametime, Viagogo and more). Never billed.
Inputs: query (required), to, from.
Every listing on one marketplace event page right now: section, row, seats, quantities it can sell, face price, fee and all-in price per ticket, cheapest first. Each marketplace captured is one billed Tickets.dev capture. A listing that disappears later may have sold, been delisted or been repriced; it is not proof of a sale.
Inputs: url (required), top, quantity, max_price.
The marketplace's own section and seat maps (SVG URLs) for an event, the cheapest all-in price per section, and the venue map's seat capacity where the marketplace gives one. Each marketplace captured is one billed Tickets.dev capture.
Inputs: url (required).
The marketplaces Tickets.dev can capture and the hosts that route to each. Never billed.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
The primary overlap is between get_listings and compare_prices/ get_seat_map, since all three capture marketplace data; however, the descriptions make the boundary fairly clear (single marketplace event page vs. multi-marketplace ranking vs. seat maps). find_events and list_marketplaces are cleanly distinct discovery tools.
All five tools follow a consistent snake_case verb_noun pattern: find_events, get_listings, compare_prices, get_seat_map, list_marketplaces. Verbs are used appropriately to signal the operation type.
Five tools is a well-scoped surface for a ticket price comparison service: two free discovery tools, three billed capture tools. Each tool earns its place with no obvious redundancy.
The core workflow (find event, compare prices, inspect listings and seat maps) is fully covered. Minor gaps exist—no dedicated event-detail tool or historical price lookup—but agents can work around these via find_events and fresh captures.
Real-time ticket listings, prices and fees across major ticket marketplaces.
Find live events, ticket price trends and each seller's tickets. Some links are affiliate links.
FrontRowTickets.com inventory for AI agents: search, deals, and seat-level options.
Travel & commerce intelligence for AI agents: search, book & price-track hotels, events, retail.
