Connect Your AI Assistant to Ticketable (MCP Server Guide)
You can now manage your Ticketable events from inside your AI assistant. Tell Claude to “set up a comedy night for the 14th with £12 early-bird tickets” and it happens — drafted in your account, ready to publish. This works through Ticketable’s MCP server (Model Context Protocol, the open standard AI assistants use to connect to tools). Here’s how to connect, client by client.
What you can do by chat
- Create events with multiple ticket tiers (created as drafts by default).
- Publish, pause, and update events — dates, venues, tiers, capacities.
- Check sales: revenue, tickets sold per tier, and individual bookings.
- Finish setting up your account — your assistant can walk you through the setup checklist: naming your organisation, choosing your booking-page handle, and generating your Stripe onboarding link.
Deliberately not available by chat: cancelling an event (which refunds every buyer), issuing refunds, and changing organisation settings — those stay in the dashboard, where they belong.
Before you start
You need a free Ticketable organiser account — but you don’t have to make one first. No account yet? Just start the connection: when your assistant sends you to Ticketable to approve access, you’ll land on the create-account page — set up your account (and organisation) right there and you’ll drop straight back onto the approval screen. Already have an account? There’s a sign-in link at the bottom of that page. Either way, you see exactly what the assistant can do before you allow it, and no passwords or keys are ever pasted into the chat.
The server address every client uses:
https://ticketable.events/api/mcpClaude (claude.ai & Claude Desktop)
- Open Settings → Connectors → Add custom connector.
- Name it Ticketable and paste the server address above.
- Click Add, then Connect — sign in to Ticketable and approve.
Claude Code (terminal)
claude mcp add --transport http ticketable https://ticketable.events/api/mcpThen run /mcp in Claude Code to authenticate via your browser.
Cursor
Add to ~/.cursor/mcp.json (or via Settings → MCP):
{
"mcpServers": {
"ticketable": { "url": "https://ticketable.events/api/mcp" }
}
}ChatGPT (developer mode)
- Enable Settings → Apps & Connectors → Advanced → Developer mode (paid plans).
- Add a connector with the server address above and complete the sign-in.
- ChatGPT asks you to confirm each write action — expected for tools that change things.
Gemini CLI
Add to ~/.gemini/settings.json:
{
"mcpServers": {
"ticketable": { "httpUrl": "https://ticketable.events/api/mcp" }
}
}The CLI discovers the OAuth flow automatically and opens your browser to approve. Note the consumer Gemini app doesn’t support custom MCP connectors yet — use the Gemini CLI.
Three things worth knowing
- Drafts first. Events are created unpublished unless you explicitly say to publish. Paid tickets can only go on sale once your Stripe account is connected (Dashboard → Settings → Stripe).
- One organisation per connection. The connection acts for whichever organisation was active when you approved it. If you belong to several, switch the active organisation in the dashboard and reconnect.
- Revoke any time. Remove the connector in your assistant’s settings and access ends.
Frequently asked questions
What can my AI assistant do once connected?
Acting as you, it can create events (as drafts by default), publish or pause them, update details and ticket tiers, list your events, and check sales and bookings — for the organisation you approve during connection. It can also help finish account setup: updating your organisation name and tagline, choosing your booking-page handle, and generating your Stripe onboarding link. It cannot cancel events, issue refunds, or change branding, fees or team settings; those stay in the dashboard.
Is it safe to connect?
You authorise the connection yourself by signing in to Ticketable and approving a consent screen — no passwords or API keys are shared with the assistant. The connection acts only on your organisation, with the same permission checks as the dashboard, and you can revoke it any time from your assistant's settings.
Which AI tools are supported?
Anything that supports remote MCP servers with OAuth: Claude (claude.ai custom connectors, Claude Desktop and Claude Code), ChatGPT (developer mode), Cursor, the Gemini CLI, and most MCP-capable agents. The consumer Gemini app doesn't support custom MCP connectors yet.
Does it cost anything?
No — the MCP server is part of Ticketable, which is free with 0% platform fees. You only need a free Ticketable organiser account.
Will the assistant publish things without asking?
Events are created as drafts unless you explicitly ask to publish, and most assistants additionally ask you to confirm write actions. Publishing paid tickets also requires your Stripe account to be connected, exactly as in the dashboard.