Ticketmaster MCP Server

A Model Context Protocol server for discovering events, venues, and attractions through the Ticketmaster Discovery API

Local serverstdio

What is the Ticketmaster MCP server?

If you already use Ticketmaster, the ticketmaster mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol server for discovering events, venues, and attractions through the Ticketmaster Discovery API.

What the server does

  • Search for events, venues, and attractions with flexible filtering:
  • Keyword search
  • Date range for events
  • Location (city, state, country)
  • Venue-specific searches
  • Attraction-specific searches

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Examples — The Examples tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: TICKETMASTER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ticketmaster's toolset — Examples — is a fair guide to whether it matches your workflow. It is maintained by delorenj; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ExamplesThe Examples tool exposed by this server.

How to install the Ticketmaster MCP server

{
  "mcpServers": {
    "ticketmaster": {
      "command": "npx",
      "args": ["-y", "@delorenj/mcp-server-ticketmaster"],
      "env": {
        "TICKETMASTER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
TICKETMASTER_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Ticketmaster to Examples.

Frequently asked questions

It connects Ticketmaster to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Examples) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ticketmaster directly.