Skip to main content
https://api.tickable.io/mcp is a Model Context Protocol server. It gives an assistant such as Claude read-only tools over the same data as the API: whoami, list_events, get_event, list_timeslots, list_ticket_types, get_availability, list_orders, get_order and list_tickets, plus sales and lookups straight from Tickable: get_stats (totals and net revenue of an activity), assistant_sales_curve (sales per day before the start, next to a previous edition), assistant_find_person (orders by the name or e-mail of the buyer or of someone on a ticket, with whether the ticket mail arrived), assistant_contact_count (how many contacts a group of visitors is and how many may get a newsletter), get_order_sources and waitlist_counts. It only offers the tools your key has the scope for, and it cannot change anything.

claude.ai, Claude Desktop and mobile

Add it as a custom connector (Settings → Connectors → Add custom connector) with the URL https://api.tickable.io/mcp. Claude sends you to Tickable to sign in and pick the organization; it gets the read scopes events.read, orders.read, tickets.read and mail.read, nothing more. A team member only hands on what their own rights in the organization allow, and a right taken away later reaches the connection within the hour. To disconnect, go to Settings → API → Gekoppelde apps in the dashboard; Claude loses access at once.

ChatGPT

Add it as a connector in ChatGPT with the URL https://api.tickable.io/mcp. ChatGPT sends you to Tickable to sign in and pick the organization, with the same read scopes as Claude.

Claude Code

Add the server and sign in from Claude Code with /mcp; it goes through the same Tickable sign-in:

With an API key

Any client that can send a header can use an API key from the dashboard instead, for example Claude Code:
Cursor and other clients that speak Streamable HTTP work the same way.