Connect an AI assistant (MCP)

Cleartix has an MCP server at https://cleartix.io/api/mcp. MCP (Model Context Protocol) is an open standard that lets AI assistants such as Claude, Cursor or your own agents use external tools. Once connected, your assistant can list your events, draft a new one from a template or starter kit, fill in ticket types and dates, set an event email or run the readiness check — from a plain-language request, with the same rules and limits as the dashboard and the REST API.

What you need

• The Pro plan — MCP uses the same access as the REST API.
• An API key (Settings → API keys) with the scopes you want the assistant to have. We recommend starting read-only (events:read, templates:read, locations:read, emails:read, stats:read) and adding events:write or emails:write on a separate key once you are comfortable with how the assistant works.
• An MCP client that can send an Authorization header. Signing in with OAuth is not yet supported, so the key travels as a bearer token: Authorization: Bearer ctk_live_….

The usual API rate limit (100 requests per minute per key) also applies to MCP calls.

Set it up

Claude Code

claude mcp add --transport http cleartix https://cleartix.io/api/mcp \
  --header "Authorization: Bearer ctk_live_…"

Start a new session and ask, for example, "Which of my events still need work before they can be published?".

Claude Desktop and claude.ai

Custom connectors in claude.ai and Claude Desktop currently expect OAuth, which Cleartix does not offer yet. Use a small bridge such as mcp-remote, which sends the header for you, in your claude_desktop_config.json:

{
  "mcpServers": {
    "cleartix": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://cleartix.io/api/mcp",
        "--header", "Authorization: Bearer ctk_live_…"
      ]
    }
  }
}

Restart Claude Desktop afterwards. The same bridge works for any other client that only speaks stdio.

Cursor

Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

{
  "mcpServers": {
    "cleartix": {
      "url": "https://cleartix.io/api/mcp",
      "headers": { "Authorization": "Bearer ctk_live_…" }
    }
  }
}

Other clients that support Streamable HTTP MCP servers with custom headers can be configured the same way: URL plus header.

What the assistant can do

Each tool needs the matching scope on your key; tools you have not granted simply are not available to the assistant. All actions are limited to your organisation, and every change is recorded in the audit log with the prefix of the key that made it.

• Events: list_events, get_event, create_event, update_event, publish_event, check_event_readiness, cancel_event, delete_event
• Ticket types & dates: set_event_ticket_types (replaces the full list), set_event_dates
• Access codes, add-ons, capacity pools & gates: manage_access_codes, manage_addons, manage_capacity_pools, manage_gates
• Event emails: list_event_emails, set_event_email, preview_event_email, send_event_email
• Templates: list_templates, get_template, create_template, update_template, delete_template, schedule_from_template, apply_template, save_event_as_template
• Locations: list_locations, create_location
• Starter kits: list_starter_kits, create_event_from_starter_kit
• Help for the assistant: describe_event_options explains every field and which features your plan allows, so the assistant does not try to use something your subscription does not include.

Destructive tools — cancel_event, delete_event, delete_template and send_event_email — require explicit confirmation: the assistant has to ask you first and pass confirm: true, so a vague request can never cancel an event or mail your attendees by accident. Errors carry the same codes as the API (for example EVENT_LIMIT_REACHED), so the assistant can explain what went wrong and suggest a fix.

Example prompts

• "Create a draft for our quiz night on 14 November from the quiz starter kit and show me the readiness check."
• "Schedule the 'Yoga Tuesday' template for every Tuesday in October at 19:00."
• "Which upcoming events have fewer than 20 tickets sold?"
• "Add an early-bird ticket type at €12 to the spring concert, limited to 50 tickets."
• "Set the reminder email for the winter market so it mentions the free parking, then show me a preview."

Whatever the assistant proposes, it only takes effect once the tool runs — you can always ask it to show the plan first.

Stay safe

1. Prefer read scopes. Give the assistant a write scope only for the task at hand, and keep it on a separate key you can delete afterwards.
2. Review before publishing. Let the assistant leave events as drafts, check them in the dashboard, and publish yourself — or ask for the readiness check first.
3. Rotate a key immediately if it ends up in a chat log, screenshot or shared config file, and delete keys you no longer use. The audit log shows exactly what a key did.
4. Never paste your key into a prompt: put it in the client configuration as shown above.