Model Context Protocol

Ask your AI assistant how the event is selling.

Connect Claude, ChatGPT, Cursor or your own code to Swarmtix, and your assistant answers from your real numbers instead of guessing. Ask it for next year's conference and it builds the draft from this year's. Setup takes about five minutes, and there is no API key to generate.

Set it up now Start free
No credit card 5 min setup No API keys 
$ claude mcp add --transport http \
    swarmtix https://swarmtix.com/mcp/v1

✓ Added server "swarmtix"
✓ Browser opened, consent approved

> How is MK Code Camp selling this week?

812 / 1,000 sold (+66 this week). Regular pass
is at 85%, Student at 59%. Net sales $61,513.
At ~9/day you sell out in ~20 days, before
the event. Want me to draft a last-call code?

What the connection gives you

47
Tools
10
Permissions you approve
5
Protocol revisions
0
API keys to manage
What changes

Four questions that stop being click paths

Real asks, phrased the way you would say them. The tools underneath are named so you can see exactly what the assistant reaches for.

Before

Open the dashboard, pick the event, open Analytics, open Tickets, copy both into a spreadsheet to compare.

After

"How is DevConf Berlin selling? Break it down by ticket type."

Revenue, tickets sold against capacity, refunds, page visits and the daily sales curve, in one answer.

swarmtix_analytics_event swarmtix_tickets_summary swarmtix_ticket_types_list
Before

Search the attendee list, cross-check the order, work out whether the promo code applied, then reply.

After

"Did the buyer on this email get their ticket for Friday?"

Their tickets, the type and price, the order it came from, and how many times it has been scanned. Never the barcode.

swarmtix_attendees_search swarmtix_orders_get
Before

Retype six ticket tiers, three dates and five checkout questions into a form, from a brief you already wrote.

After

"Copy last year's conference and move it to March."

A new unpublished draft with the same description, branding and location. The assistant sets the new dates and tiers. You review it, then publish it yourself, or let the assistant publish if you granted that permission.

swarmtix_events_duplicate swarmtix_event_dates_set swarmtix_ticket_types_create
Before

Open the discounts screen, find the offer, read the dates and the usage count, work out whether it still applies.

After

"Is EARLYBIRD still valid for the workshop, and what does it take off?"

Whether it would be accepted right now, which offer it belongs to, and the exact reduction.

swarmtix_discounts_check_code swarmtix_discounts_list
The problem

Your event data is stuck behind a dashboard

Every question is a click path

"How is early bird doing against last year?" means four screens and a spreadsheet. Your assistant could answer it in one line, if it could see your data.

Setting up an event is typing

Six ticket tiers, three dates, a promo code and five checkout questions. All of it already exists in the brief you wrote. You retype it into a form.

API keys are a liability

A key is a bearer credential. Whoever holds a copy is you, with every permission you have, until someone notices. Most platforms hand you one and call it integration.

Giving an agent full access is worse

The reason not to connect an assistant is usually the same one: one misread instruction and it refunds an order or emails four thousand people.

The solution

A server that can prepare everything and launch nothing.

47 tools: 19 that read, 28 that write. No refunds, no check-in, no bulk email. Publishing needs its own permission. The only deletes remove an unsold ticket type or parts of an unpublished online event's program; discounts and checkout questions are switched off, not erased.

Setup

Connect your assistant

Pick your client. Each block is complete on its own. You do not need an account on anything but Swarmtix.

Server URL https://swarmtix.com/mcp/v1

Claude (web and desktop)

  1. 1 Open Settings → Connectors.
  2. 2 Add a custom connector and paste https://swarmtix.com/mcp/v1.
  3. 3 Click Connect. Swarmtix opens, you sign in and approve the permissions.

ChatGPT

  1. 1 Open Settings → Connectors and create a connector.
  2. 2 Name it Swarmtix and paste https://swarmtix.com/mcp/v1 as the MCP server URL. Authentication: OAuth. Leave any API key field empty.
  3. 3 Save, then enable it in a chat under Tools.

Claude Code

Run this in your project:

claude mcp add --transport http swarmtix https://swarmtix.com/mcp/v1

Add --scope user to make it available in every project rather than the current one. Then run /mcp inside Claude Code, pick swarmtix, and authenticate.

VS Code

Create .vscode/mcp.json in your workspace, or put the same block in your user settings for every workspace:

{
  "servers": {
    "swarmtix": {
      "type": "http",
      "url": "https://swarmtix.com/mcp/v1"
    }
  }
}

VS Code prompts you to sign in the first time Copilot uses the server.

Cursor

Create .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "swarmtix": {
      "url": "https://swarmtix.com/mcp/v1"
    }
  }
}

Then open Settings → MCP and sign in.

Raw HTTP

JSON-RPC 2.0 over Streamable HTTP. Every call is a POST to the same URL. Authorize with the standard OAuth 2.1 authorization code flow and PKCE; discovery is at /.well-known/oauth-protected-resource.

curl -X POST https://swarmtix.com/mcp/v1 \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: tools/list" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Five protocol revisions are accepted. The dense, machine-readable version of this page is the reference for agents.

Capabilities

What an assistant can reach

Grouped by the permission you approve on the consent page. Approve none of them and the tools do not appear in the list at all.

Events

List and read your events by ID or URL slug, including dates, ticket types, prices, remaining stock and checkout questions.

events:read

Draft event building

Create an event from a description, duplicate last year's, set its details, images and multi-day dates, add ticket tiers, checkout questions and discounts, and build an online programme. Publishing is a separate permission.

events:write events:publish

Sales and analytics

Sales and traffic analytics for one event, and revenue rolled up across the whole organisation.

analytics:read

Orders and attendees

Read orders and the tickets in them, ticket counts on sale, sold and checked in, list attendees, and find someone's tickets by email. This is buyer personal data, and the consent page says so in those words.

orders:read attendees:read

Discounts

List promo codes and offers, check whether a code is valid for an event and what it takes off, create a new one, change it, or switch it off.

discounts:read discounts:write

Organisation reference data

Your teams and your saved venues. Not billing, not payouts, not account settings. No permission covers those.

organization:read profile

And what it cannot do, on purpose

These are not gaps we intend to close. The worst outcome of a misread instruction should be that a draft event got edited.

Refunds and charges
Moves real money.
Publishing without the permission
Going public stays your click unless you grant events:publish.
Check-in and barcode scanning
The product has no undo for it.
Bulk attendee email
Nothing recalls a send.
Guest-list import
Creates orders and emails tickets in one step.
Deleting sold items
Only unsold ticket types and unused program items can be removed. Discounts and checkout questions are switched off, not erased.
Returning ticket barcodes
They are the credential for admission.
Registering a webhook
Pointing order data at a URL stays a human action.
Permissions

The ten permissions, in plain English

The middle column is the exact sentence you will see on the consent page. Nothing here is a paraphrase of it.

Permission What the consent page says What that covers
profile Read your name and email address. Who you are and which organisation this connection covers. Every connection includes it.
events:read Read your events, event dates and ticket types. Events, dates, ticket types, prices, remaining inventory and checkout questions. Not who bought anything.
events:write Create, update and remove unsold parts of your events: details, images, dates, ticket types, checkout questions and an online event's program (talks, speakers, categories, hosts). Nothing is published. Create an event, duplicate one, change its details and images, set its dates, add, change and remove ticket types (only unsold ones can be deleted), add, change and switch off checkout questions, and build an online event's talks, speakers, categories and hosts. Cannot publish.
events:publish Publish your events, which puts their tickets on sale, and unpublish them. Only an event with nothing missing can be published. Nobody is emailed or refunded. Publish a finished event so its tickets go on sale, and take it off sale again. A publish is refused while anything is missing. Cannot create or change anything else, and cannot move money.
orders:read Read your orders and attendee lists, including ticket buyers' names and email addresses. Personal data. Order buyer first name, last name and email address; ticket attendee first and last name. Plus ticket counts on sale, sold and checked in.
attendees:read Read your orders and attendee lists, including ticket buyers' names and email addresses. Personal data. Attendee lists and lookup by email address. Cannot email anyone and cannot check anyone in.
analytics:read Read sales and attendance figures for your events. Sales and revenue analytics per event, and a roll-up across the organisation. Totals only, no names.
discounts:read Read your discount codes and promotions. Promo codes and discount offers, and whether a given code is currently valid for an event.
discounts:write Create, update and switch off discount codes, promotions and access codes. Creates, changes and switches off codes. An access code unlocks a hidden ticket type. It does not publish or move money.
organization:read Read your organization's teams and venues. Your teams and saved venue layouts. Not billing, payouts or account settings; no permission covers those.

Orders and attendees share one sentence on the consent page on purpose: they describe the same access to the same personal data, and printing two softer lines instead of one clear one would understate it.

Limits

60 requests per minute per organisation, on a sliding window, counted across every connection. Over it, the assistant gets a clear "retry in N seconds" and carries on.
50 results per page by default, 200 at most. A list that does not fit says how much it cut and how to ask for the rest.
No per-call charge. The connection costs nothing beyond your normal per-ticket fee.

Revoking access

Go to Settings → Developers → Connections and revoke the connection.

It takes effect immediately, on that connection's very next call, not whenever its token happens to expire.

Revoking one assistant does not affect another; each connection is its own grant.

Open connections

Questions and troubleshooting

Which assistants can connect?+

Any client that speaks MCP over HTTP. Claude, ChatGPT, Claude Code, VS Code, Cursor, and your own code all work against the same URL. The server supports five protocol revisions, from 2024-11-05 through 2026-07-28, so older clients and current ones both connect without you choosing a mode.

Is there an API key to generate?+

No. You add the server URL, a Swarmtix page opens in your browser, you pick the organisation and approve the permissions. There is nothing to copy, paste or store. The older 90-day API token used by Zapier and the REST API still works and is unchanged.

Which URL do I paste?+

https://swarmtix.com/mcp/v1 - with the /v1 on the end. The page you are reading now lives at /mcp and is written for people; /mcp/v1 is the endpoint your assistant talks to. Pasting the wrong one is the most common reason a connection fails to start.

Can an assistant publish an event or take money?+

No. Refunds, charges, check-in, bulk attendee email, guest-list import and every delete of an event, order or attendee are outside the tool catalog. An assistant can prepare an event completely. Opening it to the public needs a separate permission, publish, which you approve on its own. Without it, publishing stays your click.

What can it actually see about my buyers?+

Only what you grant. The orders and attendees permission covers buyer first name, last name and email address, and attendee first and last names. The consent page says so in those words before you approve it. Ticket barcodes and security codes are never returned by any tool, because they are the credential that gets someone through the door.

How do I revoke access?+

Settings, then Developers, then Connections. Revoking takes effect on the next call rather than whenever a token happens to expire, because access tokens are checked against our store on every request.

What does it cost?+

Nothing beyond standard Swarmtix pricing: $0.99 + 1.5% per paid ticket, and free events are always free. There is no separate charge for connecting an assistant and no per-call fee.

What are the limits?+

60 requests per minute per organisation, sliding window. Over that you get a 429 with a Retry-After header. List tools page at 50 results by default and 200 at most, and a truncated result always says how much it cut and how to get the rest.

I belong to more than one organisation. What happens?+

One connection covers one organisation. Add the server once per organisation and name each connection so you can tell them apart. A token can never reach data outside the organisation it was granted for.

The consent page never opened+

Your client blocked the pop-up or the browser it chose is not signed in. Open the URL it printed by hand, sign in, and approve. The client picks the token up on its own.

The assistant says a tool does not exist+

You did not approve the permission that tool needs. Reconnect and approve it, or ask for something covered by what you did approve. Tools you cannot use are hidden rather than refused.

I get 401 after a while+

Access tokens are short-lived by design; the client refreshes them silently. If it cannot, the connection was revoked. Reconnect from Setup above.

The wrong organisation answers+

One connection covers one organisation. Add the server again, pick the other organisation on the consent page, and name the connection so you can tell them apart.

Still stuck? Email [email protected], or read the full documentation.

Pricing

The server costs nothing extra

You pay the same per-ticket fee whether you use the dashboard, the REST API or an assistant. There is no developer tier and no per-call charge.

Pay as you go

$0.99 + 1.5%

per paid ticket sold · free tickets are free

Dashboard, REST API and MCP server all included
No developer tier, no per-call charge
Instant payouts to your Stripe
Revoke any connection in one click
Start selling tickets

Full plan comparison on the pricing page

Related links

MCP reference for agents
Endpoint, protocol revisions, client config blocks, and the full tool table.
MCP documentation
Overview, per-client setup, the ten scopes, and a page per tool.
MCP integration
What an assistant can reach in your account, and the four steps to connect it.
Zapier integration
Move the same data with no assistant in the loop.
Developer conference ticketing
The rest of what Swarmtix does for tech conferences.
Pricing
$0.99 + 1.5% per paid ticket. Free events are always free.

Connect your assistant in five minutes.

Add one URL, approve one consent screen. No key to generate, nothing to store.

Set it up now