Loading
We use analytics (Amplitude, with session replay) to understand how Ticketted is used and find broken things faster. Sellers can also create campaign links that set a 30-day attribution cookie and a 1-year visitor-id cookie so they can see which channels send their visitors. Essential cookies are always on; analytics are off until you accept. Cookie details.
Ticketted exposes an MCP server, so you can browse events and manage your tickets straight from Claude, ChatGPT, Cursor, and other AI tools.
Browse events, check availability, and validate promo codes. Nothing personal; add it anonymously.
https://www.ticketted.com/mcp/publicYour tickets, refunds and membership, plus booking free events. Your AI tool will ask you to sign in with Ticketted.
https://www.ticketted.com/mcp/meEasiest: open Settings → Connectors → Add custom connector and paste a URL above — Claude walks you through sign-in for the personal one. Or, in the desktop app's claude_desktop_config.json:
{
"mcpServers": {
"ticketted": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://www.ticketted.com/mcp/me"
]
}
}
}Add to ~/.cursor/mcp.json(or a project's .cursor/mcp.json), then approve the sign-in prompt:
{
"mcpServers": {
"ticketted": {
"url": "https://www.ticketted.com/mcp/me"
}
}
}In Settings → Apps & Connectors → Advanced → Developer mode, create a new app and paste a URL above. The public URL connects with no auth. For the personal URL, set Authentication to OAuth — ChatGPT auto-discovers the endpoints — then adjust the OAuth scope settings before creating it:
Required for the personal URL to sign in
profile and email checked. Uncheck openid, offline_access, public_metadata and private_metadata.Why: our sign-in provider doesn't grant openid / offline_access to auto-registered apps, so requesting them makes the sign-in window close instantly with an invalid_scope error. profile + emailis all that's needed.
Tip: start with the public URL to try it with no setup, then switch to the personal URL once you want to see your own tickets.