TicketSource MCP server

An MCP server that lets Claude, ChatGPT and other MCP clients work with a TicketSource box office: events, performance dates, bookings, seats and customers. It is built on TicketSource's public API and its published OpenAPI spec.

Once it's connected, an organiser can ask things like:

• "What's on in the next two weeks?"

• "Who's booked for tomorrow's Macbeth, and how much have we taken after fees?"

• "Find Sam Evans. What else has she booked this year, and are there notes on her record?"

• "List everyone in row C for Friday with their booking references."

Tools

Related MCP server: Line-Up MCP server

Setup

Requires Node 18 or later.

npm install
npm run build

Create an API key in TicketSource under Settings > API.

Claude Desktop: add this to claude_desktop_config.json:

{
  "mcpServers": {
    "ticketsource": {
      "command": "node",
      "args": ["/absolute/path/to/ticketsource-mcp/dist/index.js"],
      "env": { "TICKETSOURCE_API_KEY": "skl-your-key" }
    }
  }
}

Claude Code:

claude mcp add ticketsource -e TICKETSOURCE_API_KEY=skl-your-key -- node /absolute/path/to/ticketsource-mcp/dist/index.js

Safety defaults

• Read-only unless TICKETSOURCE_ALLOW_WRITES=true. Read tools carry the MCP readOnlyHint annotation.

• Attendee emails and phone numbers are only returned when the assistant explicitly asks for them (include_contact_details).

• IDs are validated against the formats in your spec before any call is made.

• Requests are spaced to stay under the 240 calls per minute limit, and 429 responses are retried using Retry-After.

• A rejected API key produces a message that tells the user where to fix it.

Tests

npm test

The test suite:

1. Validates every fixture record against the component schemas in TicketSource's published OpenAPI spec. The spec is downloaded from github.com/ticketsource/openapi-spec to spec.yaml on the first run.

2. Starts a local mock of the API that serves those fixtures with JSON:API pagination, a 401 on a bad key, 404s, and a one-off 429.

3. Starts the built server and drives it over stdio with the official MCP client: 15 checks covering every tool, pagination, refunds and donations in totals, the 429 retry, the write gate, contact-detail redaction, and that every request used the Bearer key and a documented endpoint.

Status

This is a working prototype. It has not yet been run against the live API, because it was built without a TicketSource account. Two things to confirm on a real account:

• The body accepted by POST /customers/{id}/notes. The server sends {"data": {"type": "customer_note", "attributes": {"description": "..."}}} as documented.

• The format of start on dates. It is parsed as ISO 8601; dates that can't be parsed are kept rather than dropped.

The API has no server-side customer search, so find_customers pages through the customer list (100 per call, 10 pages by default). On large accounts, a search parameter on GET /customers would make this much cheaper.

Going to production

This version runs locally over stdio, with the organiser's own API key. For organisers to connect from claude.ai or ChatGPT without handling keys, the next step is a remote server (Streamable HTTP) behind OAuth, hosted by TicketSource, and then a listing in the Claude and ChatGPT connector directories.

Licence

MIT. Built by Alexandru Dragoș (alexandru.dragos96@gmail.com) with an AI agent (Claude) working under his direction.