AI

Name: AI
Author: Tickets-dot-dev

by Tickets-dot-devversion 0.1.0i★ –iComputer or cloud

Registry nameio.github.Tickets-dot-dev/ai

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: TICKETS_DEV_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: TICKETS_DEV_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ai": {
      "command": "npx",
      "args": [
        "-y",
        "tickets-dev-mcp"
      ],
      "env": {
        "TICKETS_DEV_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http ai https://api.tickets.dev/mcp --header 'Authorization: Bearer {api_key}'

Or run it on your computer

claude mcp add ai --env TICKETS_DEV_KEY=your-value -- npx -y tickets-dev-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ai": {
      "url": "https://api.tickets.dev/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ai": {
      "command": "npx",
      "args": [
        "-y",
        "tickets-dev-mcp"
      ],
      "env": {
        "TICKETS_DEV_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ai": {
      "type": "http",
      "url": "https://api.tickets.dev/mcp",
      "headers": {
        "Authorization": "Bearer {api_key}"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ai": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "tickets-dev-mcp"
      ],
      "env": {
        "TICKETS_DEV_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

TICKETS_DEV_KEY secret required env
Your Tickets.dev API key, from https://tickets.dev/pricing
Authorization secret HTTP header
Bearer followed by your Tickets.dev API key, from https://tickets.dev/pricing. Optional: clients that support OAuth can sign in at tickets.dev instead.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Tickets-dot-dev, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32466 servers in this category
Published to the registry more recently than 77% of the other 32466 servers in this category
Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AI safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TICKETS_DEV_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

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:

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

codex plugin marketplace add Tickets-dot-dev/ai

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

codex mcp login tickets-dev

Cursor

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

Gemini CLI

Run this command:

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:

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:

"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
`find_events`	Finds upcoming events and their URL on every marketplace. Free.
`get_listings`	Returns every listing on one event page, with all-in prices.
`compare_prices`	Ranks one event's listings across marketplaces by all-in price.
`get_seat_map`	Returns the section and seat maps, the cheapest price per section and, where the map gives it, venue capacity.
`list_marketplaces`	Lists 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:

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.

Development

npm install

node --test # offline tests TICKETS_DEV_E2E_KEY= node --test # end-to-end through api.tickets.dev/mcp (uses a few captures)

License

MIT. Not affiliated with any ticket marketplace.

AI

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

HotCodePush

README from the maker

Tickets.dev AI

What you can ask

Use the API with any agent

Agent skill

Plugins

Claude Code

Codex

Cursor

Gemini CLI

Grok Build

MCP server

API key

More from Tickets.dev

Development

License