Available Now

MCP Integration

Connect an AI assistant directly to SwarmTix with the Model Context Protocol. Claude, ChatGPT, Claude Code, VS Code and Cursor all talk to the same server URL, so you can ask about ticket sales in plain language and let the assistant build a draft event for you. There is no API key to generate or store.

Connect MCP View setup guide

Free to connect. No additional fees beyond standard SwarmTix pricing.

Capabilities

What you can do with MCP

Powerful features that connect your events with MCP.

24 tools across events, orders, attendees, analytics and discounts

Read sales figures, orders, attendee lists and revenue roll-ups

Create draft events, ticket types, event dates and checkout questions

Duplicate last year’s event as the starting point for this year’s

Create promo codes and check whether a code is valid

OAuth 2.1 sign-in with PKCE, so no API key is ever created or stored

Nine scopes you approve individually on a Swarmtix consent page

One-click revoke that takes effect on the next call, not at token expiry

Setup Guide

How to connect MCP

Follow these steps to integrate MCP with SwarmTix in minutes.

Add the server URL in your assistant

Paste https://swarmtix.com/mcp/v1 into your client's connector or MCP settings. In Claude Code that is: claude mcp add --transport http swarmtix https://swarmtix.com/mcp/v1

Approve the connection

A Swarmtix page opens in your browser. Sign in, pick the organisation this connection is for, and read the permission list. It is written in plain English, not scope names.

Grant only what the assistant needs

Reading orders and attendees exposes your buyers’ names and email addresses, and the consent page says so. Leave out any permission you do not want the assistant to have.

Start asking

Tools you granted appear in your client straight away, along with four ready-made prompts: readiness check, sales review, attendee reconciliation, and post-event summary.

Start Integration Setup

Use Cases

How organizers use MCP

Real-world scenarios where this integration shines.

Ask how an event is selling and get the real numbers, not a dashboard

Check whether an attendee received their ticket, by email address

Build next year’s conference as a draft from this year’s event

Add a full set of ticket tiers from a written brief in one step

Review revenue across every event without exporting a spreadsheet

Frequently Asked Questions

Which assistants does this work with?

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

Do I need an API key?

No. Authorization is OAuth 2.1 with PKCE. You approve the connection on a Swarmtix page and there is nothing to copy, paste or store. The older 90-day API token used by Zapier and the REST API is unaffected and keeps working.

Can an assistant publish my event or issue a refund?

No. Refunds, charges, publishing, check-in, bulk attendee email, guest-list import and every delete are outside the tool catalog, so no assistant can reach them however it is asked. Every event an assistant creates lands as a draft for you to review.

What personal data can it see?

Only what you grant. The orders:read scope covers buyer first name, last name and email address, and attendee first and last names. 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 disconnect an assistant?

Go to Settings, then Developers, then Connections, and revoke it. Access tokens are checked against our store on every call, so a revoked connection stops working on its next request rather than whenever its token would have expired.

Does it cost anything extra?

No. The MCP server is included in standard SwarmTix pricing of $0.99 + 1.5% per paid ticket, and free events are always free. There is no developer tier and no per-call charge.