AI

Name: AI
Author: Tickets-dot-dev

作者：Tickets-dot-dev版本 0.1.0i★ –i电脑或云端

注册名称io.github.Tickets-dot-dev/ai

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 电脑或云端
传输方式: stdio, Streamable HTTP
分类: 其他
你需要填写：TICKETS_DEV_KEY, Authorization

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
需要你自己填写： TICKETS_DEV_KEY, Authorization

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

在云端运行无需安装任何东西，通过互联网连接
npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

或者在你的电脑上运行

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

或者在你的电脑上运行

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

或者在你的电脑上运行

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

或者在你的电脑上运行

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个地址需要在请求的 header 中放入密钥，而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

TICKETS_DEV_KEY 机密必填 env
Your Tickets.dev API key, from https://tickets.dev/pricing
Authorization 机密 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

我们还没有读取这个服务器的工具列表；我们会轮流检查各个端点。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Tickets-dot-dev 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
… 尚未检查
端点有响应
尚未检查；我们会轮流检查各个端点
… 尚未检查
使用 OAuth 登录
尚未检查；我们会轮流检查各个端点
… 尚未检查
工具描述中没有隐藏指令
尚未检查；我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32505 个服务器的 0%
发布到注册中心的时间比此分类中其他 32505 个服务器的 77% 更新
基础检查结果等于或优于此分类中其他 32505 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

AI 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：TICKETS_DEV_KEY, Authorization

它在我的电脑上运行还是在云端？

两种方式都可以：安装在你的电脑上，或者连接云端版本。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.0）于10天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, topo^alpin

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211昨天更新

安装

topo^alpin

作者：topoalpin.app

Avalanche bulletins and mountain weather forecasts for any place in the Alps.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

或者在你的电脑上运行

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

topo^alpin

作者的 README

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