Swarmtix MCP Server

Connect an AI assistant — Claude, ChatGPT, Claude Code, VS Code, Cursor — directly to your Swarmtix organisation. Once connected, you can ask questions about your events in plain language and get answers from your real data, and you can let the assistant do the setup work: build a draft event, add ticket types, create a promo code.

Quick Start

1. Open your assistant's connector or MCP settings
2. Add a new server with the URL https://swarmtix.com/mcp/v1
3. Your browser opens a Swarmtix consent page
4. Sign in, pick the organisation, and review what the assistant is asking for
5. Click Allow

That's it. There is no API key to generate, copy or store. See Connecting for the exact steps in each client.

What You Can Do With It

The server exposes 24 tools. In practice they cover four jobs organisers do every week.

See how sales are going

Ask "how is the spring conference selling?" and the assistant pulls the real numbers — tickets sold per type, remaining inventory, gross revenue, and the sales curve over time. It can roll several events up into one answer, or compare this event to the last one.

Answer a question about an order or an attendee

Ask "did [email protected] get her ticket?" and the assistant looks up her tickets for that event. It can read an order, list attendees, and check whether a promo code is valid and what it takes off.

Set an event up

Ask it to create a new event from a description, copy last year's event as a starting point, add a set of ticket tiers, set the dates for a multi-day run, or add the custom questions you want buyers to answer at checkout.

Every event an assistant creates lands as a draft. Nothing in the catalog can put an event in front of the public.

Editing an existing event's own record — its name, description, venue, host or branding — is not available through MCP yet. An assistant can build a draft and fill in its schedule, tickets, questions and discounts; the event's own details are edited in the dashboard.

Check the details before you open the doors

Ask "is Friday's event ready?" and the assistant walks the checklist — dates set, ticket types priced and in stock, checkout questions in place, discounts configured.

Beyond Tools

Two other things sit alongside the catalog, both gated by the same permissions.

Resources let an assistant attach an event, or its sales figures, to a conversation as context rather than spending a tool call fetching it — swarmtix://events/spring-summit-2026 and swarmtix://events/spring-summit-2026/analytics.

Prompts are four ready-made requests for the jobs above: a readiness check, a sales review, an orders-against-attendees reconciliation, and a post-event write-up. Pick one in your client, name the event, and it drops the whole request into the conversation for you.

What It Deliberately Cannot Do

This is the part worth reading carefully, because it is a design decision rather than a gap we intend to close.

The catalog is reads plus safe writes. The worst outcome of a misunderstood instruction is that a draft event was edited. It is never that a customer was refunded, or that four thousand people got an email.

The following are not in the catalog, and an assistant connected to Swarmtix cannot do them no matter how it is asked:

Publishing is the boundary

The clearest way to hold the line in your head: an assistant can prepare an event completely and cannot launch it. It will hand you a finished draft. You publish.

How Your Data Stays Separate

One authorized connection covers one organisation. The organisation is baked into the token issued when you approved the connection — it is never something the assistant passes in as a parameter, so it cannot be changed by the assistant, by a prompt, or by anything in a document the assistant happens to be reading.

Every tool that touches an event re-checks that the event belongs to your organisation before it does anything else. An event ID from another organisation returns a not-found error and reveals nothing about it.

If you belong to more than one organisation, authorize once per organisation. Most clients let you add the same server twice under different names.

Addressing an Event

Anywhere a tool takes an event, it takes either the event's id or its URL slug — the last part of the public event address. spring-summit-2026 works as well as a GUID, so you can ask about an event by the name you know it by rather than looking an identifier up first.

Everything else is addressed by an id a read tool gave you: scheduled dates from swarmtix_event_dates_list, ticket types from swarmtix_ticket_types_list, orders from swarmtix_orders_list.

Limits Worth Knowing

• List tools are paged. 50 results by default, 200 at most, using cursors rather than page numbers so that tickets selling mid-read cannot make rows repeat or go missing. Asking for more than 200 is refused rather than quietly reduced, and a page that does not cover everything ends with the cursor for the next one.
• Responses are capped at 60,000 characters. A result too large is truncated and says it was truncated, with the total and how to get the rest. Silent truncation is worse than a stated one.
• 60 requests a minute, per organisation. Counted across all your credentials together. Going over returns a 429 with a Retry-After telling the client how long to wait; well-behaved clients back off on their own.
• Errors are sentences. A tool that cannot do what you asked explains why in plain English, not a numeric code.

What It Never Returns

Your buyers' names and email addresses are readable by an assistant you grant orders:read or attendees:read — that is the point of those permissions, and the scopes page says so plainly before you approve anything.

Ticket barcodes and security codes are different, and no tool returns them under any permission. A barcode is the credential that gets someone through the door; a copy of one is a free ticket. They are stripped before any result is built.

Where to Go Next

Use Cases

• Weekly sales review — ask one question instead of opening five analytics pages
• Support lookups — find a buyer's tickets without leaving the conversation you are already in
• Event setup from a brief — paste the event description you were sent, get back a draft with tickets priced
• Season rollover — duplicate last year's event, adjust the dates, review the draft
• Pre-event checks — a standing prompt that walks the readiness list before every door opens