Skip to content

Ticket Fairy MCP server

Let your AI assistant run your events

Ticket Fairy speaks the Model Context Protocol, the standard AI assistants use to work with a system directly. Point Claude Code, Cursor or another MCP client at it and ask about live sales or hand it routine setup work. Routine changes run when the assistant calls them. Cancellations and deletions stop for your approval by default.

The MCP server runs on your own machine, signs in as you, and can only do what your Ticket Fairy role already allows.

Connect your assistant See the guardrails

Included with the Ticket Fairy CLI. Free with your account. No hosting, no client secrets, no separate login.

Your AI client's config 
{
  "mcpServers": {
    "ticketfairy": {
      "command": "ticketfairy",
      "args": ["mcp", "--read-only"]
    }
  }
}

That is the entire client configuration once you install the CLI and sign in. Remove --read-only when you want the assistant to make changes as well as read.

What you can ask for

Your assistant gets named Ticket Fairy actions and live event data, so it can answer from your events instead of interpreting a dashboard screenshot.

"How is Saturday selling?"

Your assistant reads live sales, check-in counts and order detail for the event you are talking about, instead of you opening four screens to answer it.

"Set up next month's show like the last one"

Your assistant can clone an event, add ticket types, price them and schedule the on-sale. Routine changes run when the assistant calls them. By default, destructive changes stop and ask you before they run.

"Cancel this free order"

Your assistant can inspect the order, show you what it found and ask for approval before it cancels the order.

"Pull the numbers into my own report"

Your assistant works from structured data rather than a screenshot, so what it hands back can go straight into a spreadsheet, a summary or another tool.

Connect your AI client

No hosting to arrange, no keys to request, and nothing to expose to the internet.

  1. Install the CLI

    The CLI includes the MCP server and requires Node 20 or newer.

    Terminal 
    $ npm install -g ticketfairy

  2. Sign in once

    Opens your browser. The server borrows this sign-in, so there is nothing else to configure.

    Terminal 
    $ ticketfairy login

  3. Add it to your AI client

    Paste the copied configuration into your client's MCP settings, then restart the client.

    Then ask 
    "Which of my events are selling slowest this week?"
"How many people have checked in tonight?"
"Clone last month's show for the 14th."

On a server or in a shared runner, set TICKET_FAIRY_API_KEY to a Personal Access Token instead of signing in. If the server starts with no credentials at all, it says so immediately rather than letting the assistant fail one question at a time.

What the assistant can reach

The MCP server exposes named actions instead of asking your assistant to interpret a dashboard screenshot. The general-purpose api tool covers other endpoints with GET requests by default.

  • Context Read, set or clear the active brand and event, and check both before making a change.
  • Brands List and select your brands, use list_brand_geographics_scopes to find the available series, venue, country and city filters, or use brand stats with get_brand_stats for whole-brand geographic and demographic insights. Geographic reports can be filtered by event, series, venue, country or city.
  • Events List and read events and sales performance, plus create, update, publish, unpublish, postpone, disclose a date, cancel, reinstate, clone and delete.
  • Tickets List ticket types, and create, update or delete them.
  • Orders List and inspect orders, cancel a free order or approve an order awaiting review. Approval may capture an authorised card payment and issues the tickets.
  • Customers Search your CRM by name, email or phone, then open a customer's full record.
  • Add-ons List add-ons, and create, update or delete them.
  • Invitations List invitations, and resend or cancel one.
  • Promotions List promo codes, and create, update or disable them.
  • Check-in Read live check-in stats and the tickets behind them.
  • Webhooks List, read, create, update and delete webhooks.
  • Team List team members, and invite, change or revoke access.
  • Tours List and read tours and their members, and create, update or delete a tour.
  • Tables List table types, and create or update them.
  • Messaging List campaigns, and send one after you approve it in your compatible AI client.
  • Vault Read-only: account, balance, transactions and transfers.
  • Assets Upload an image or file and get back the URL to use in a change.
  • Auth Report who the server is signed in as. The token value is never shown.
  • Direct API access A general-purpose call for anything without a dedicated tool. GET-only unless you start the server with --enable-api-passthrough.

Raw API writes are a separate choice. Start the server with --enable-api-passthrough to add POST, PATCH, PUT and DELETE to the api tool. Raw API writes do not use the separate approval prompt provided for named destructive actions, and this flag cannot be combined with --read-only.

Vault tools are invitation only. They read banking state for brands with Vault access, and they never write.

You decide how much it can do

The mode is set in the config file, before the server starts. It is not something the assistant can talk its way out of partway through a conversation.

Choose how the Ticket Fairy MCP server starts and what it allows.
How you start it What the assistant can do Detail
ticketfairy mcp --read-only Reads only Where to start Only the reading tools exist. The assistant can answer questions about your events and cannot change anything, whatever it is asked to do.
ticketfairy mcp Reads and makes routine changes Routine changes run when the assistant calls them. Before a destructive action runs, your compatible AI client asks you to approve it. The model cannot answer that prompt for you.
ticketfairy mcp --allow-destructive Skip destructive-action prompts Keeps all named Ticket Fairy actions available but removes the separate prompt before every destructive action. Use it only when you accept assistant-initiated destructive actions.

Destructive approval happens in your client

Before a deletion or cancellation runs, your compatible AI client asks you to approve it and waits for your answer. The model cannot answer. If your client cannot show MCP approval prompts, make that change in your Ticket Fairy dashboard.

Routine changes, such as adding a ticket type, run when the assistant calls them. Start the server in read-only mode and no tools that make changes are registered.

Underneath both, your usual permissions still apply. The server acts as you, with your role and your brands. Use the same access and review process your organisation applies to work in the dashboard.

The MCP server runs on your machine

Your AI client starts the server as a local process and talks to it over its own input and output. There is no Ticket Fairy MCP address on the internet for an assistant to connect to on its own, so there is nothing to set up on our side and nothing running when you are not using it.

The server runs locally, but the event, order and customer data it returns goes to your AI client and may be sent to that client's model provider. Use a client and account your organisation approves, and check its data-retention policy before connecting live event data.

Your default brand is stored in the CLI profile. The active event and any MCP-only context disappear when that process stops. Use a separate named profile for each workspace, and check the selected brand and event before any change.

When a request fails, read its message before retrying. Then ask your assistant to repeat the selected brand and event so you know the next call is working in the right place.

Install the CLI What else the CLI does

Already using AI inside Ticket Fairy?

Fai is the co-pilot built into your dashboard: free for your team, with nothing to install, and limited to your Ticket Fairy permissions. The MCP server connects the assistant you already work in to its own set of Ticket Fairy tools, on your machine and next to your other tools. Both use your Ticket Fairy permissions and live platform data.

Meet Fai

Questions about the MCP server

It is the standard way an AI assistant plugs into a system it was not built with. Instead of the assistant guessing its way around a web page, it gets a named list of actions it can take and data it can read. Ticket Fairy publishes that set, so any assistant that speaks the protocol can work with your events.

It runs on your own computer, started by your AI client. There is no Ticket Fairy address on the internet an assistant can connect to on its own. It is there only while you are using it.

It can only use the tools the mode you chose registers. In read-only mode there is nothing to change. In default mode, routine changes run when the assistant calls them, while destructive actions stop and ask you in a compatible AI client. The sign-in also carries your role, so your assistant cannot reach a brand you cannot access.

It borrows the sign-in the CLI already has, so ticketfairy login once is enough. There is no separate account, no client secret, and no password for the assistant to hold.

The default brand stays in your active CLI profile. The active event and other MCP context last only while the server process runs. Check the selected brand and event before asking your assistant to make a change.

Fai lives inside Ticket Fairy, free for everyone on your team and with nothing to install. The MCP server is for the assistant you already work in, on your own machine, alongside your code and your other tools. Both use your Ticket Fairy permissions and live platform data.

Ticket Fairy in full: event ticketing and registration platform, with the features, pricing and support behind this page.

Further Reading

Best Event Ticketing Software Compared Early Bird & Tiered Pricing Strategies Using Ticketing Data to Improve Your Events

Give your assistant live event data and controlled actions

Install the CLI, sign in once, and paste the configuration into your AI client. Start read-only, then enable tools that make changes when you are ready.

Install the CLI Create a free account Book a demo

Questions about connecting your assistant? Email [email protected].

Get Started for Free Book Demo