Ai

io.github.Tickets-dot-devPublished by GitHub account Tickets-dot-devv0.1.0Updated Nov 5, 2026

Live ticket prices, listings and seat maps for AI agents.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Tickets.dev MCP server that gives an assistant live ticket listings, all-in prices and seat maps from major resale marketplaces.

What you can do
  • Find upcoming events and their marketplace URLs
  • List every listing on one event page with all-in prices
  • Rank one event's listings across marketplaces by all-in price
  • Return section and seat maps with the cheapest price per section and venue capacity where available
  • List the supported marketplaces
When to use it
Useful when someone wants to compare ticket prices across marketplaces, inspect seat maps and per-section pricing, or track get-in prices for upcoming shows. It is read-only, so it suits research and price checking rather than buying.
Requirements
Either the hosted Streamable HTTP endpoint or the local npm package tickets-dev-mcp, which bridges to the same hosted server. Authentication is required: OAuth sign-in at tickets.dev, or an API key sent as an Authorization bearer header or in the TICKETS_DEV_KEY environment variable. Network access to api.tickets.dev.
Before you install
Each capture of one event on one marketplace is billed like a direct API call, so tool use can cost money; one call uses at most 15 captures and up to 3 calls run at once per account. The API key is a secret and should not be pasted into chat. The tools only read data and cannot buy, hold or list tickets. Listing data comes from third-party marketplaces.

Installation

In SourceWeft

  1. Open Ai in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Tickets-dot-dev%2Fai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ai": {
      "type": "http",
      "url": "https://api.tickets.dev/mcp"
    }
  }
}

README

[tickets.dev AI: ask for the cheapest 2 seats for the Eagles at Sphere, get the same seats priced on TickPick, SeatGeek, Vivid Seats and Gametime]

Tickets.dev AI

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.

What you can ask

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.

Use the API with any agent

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:

bash
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"

Agent skill

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.

Plugins

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.

Claude Code

Run these commands in Claude Code:

bash
/plugin marketplace add Tickets-dot-dev/ai/plugin install tickets-dev@tickets-dev

Then run /mcp, pick tickets-dev and choose Authenticate to sign in.

Codex

Run this command:

bash
codex plugin marketplace add Tickets-dot-dev/ai

Then restart Codex, install Tickets.dev from the Plugins directory, and sign in:

bash
codex mcp login tickets-dev

Cursor

Install the plugin from cursor.directory, or use the MCP server.

Gemini CLI

Run this command:

bash
gemini extensions install https://github.com/Tickets-dot-dev/ai

Then run /mcp auth tickets-dev in Gemini CLI to sign in.

Grok Build

The plugin is coming to the Grok Build marketplace. Until then, use the MCP server.

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:

bash
claude mcp add --transport http tickets-dev https://api.tickets.dev/mcp

Then 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:

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:

json
{  "mcpServers": {    "tickets-dev": {      "command": "npx",      "args": ["-y", "tickets-dev-mcp"],      "env": { "TICKETS_DEV_KEY": "tk_live_..." }    }  }}
ToolWhat it does
find_eventsFinds upcoming events and their URL on every marketplace. Free.
get_listingsReturns every listing on one event page, with all-in prices.
compare_pricesRanks one event's listings across marketplaces by all-in price.
get_seat_mapReturns the section and seat maps, the cheapest price per section and, where the map gives it, venue capacity.
list_marketplacesLists supported marketplaces. Free.

The tools only read data. They can't buy, hold or list tickets.

API key

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:

bash
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.

More from Tickets.dev

Development

bash
npm installnode --test                                  # offline testsTICKETS_DEV_E2E_KEY=<your key> node --test   # end-to-end through api.tickets.dev/mcp (uses a few captures)

License

MIT. Not affiliated with any ticket marketplace.

Source: README.md at commit 921b755

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts