tickets-dev-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKETS_DEV_KEY | Yes | Your Tickets.dev API key (e.g. tk_live_...). Required for the plugins and MCP server. | |
| TICKETS_DEV_MAX_CAPTURES | No | Maximum number of captures per session, used to limit spending. Each capture of one event on one marketplace is billed. | 25 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_eventsA | 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. |
| get_listingsA | 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. |
| compare_pricesA | 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). |
| get_seat_mapA | 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. |
| list_marketplacesA | The marketplaces Tickets.dev can capture and the hosts that route to each. Never billed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.