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
- Any Cleartix plan: MCP is included on Free, Studio and Pro. (The REST API itself needs Studio or Pro.)
- A Cleartix account that is a member of the organisation. In claude.ai, Claude Desktop and ChatGPT you simply sign in when the connector asks you to; you pick the organisation and the scopes on the consent screen. No API key is needed.
- Only for command-line tools (Claude Code, Cursor, your own agents) that cannot open a sign-in window: an API key (Settings → API keys) with the scopes you want the assistant to have, sent as
Authorization: Bearer ctk_live_….
Whichever way you connect, we recommend starting read-only (events:read, templates:read, locations:read, emails:read, orders:read, attendees:read, stats:read) and adding events:write, emails:write, orders:write (refunds, order cancellations and booking bank transfers as paid), tickets:write (resending tickets) or checkin:write (checking in and undoing check-ins) once you are comfortable with how the assistant works. Five further scopes unlock the newer tools: waitlist:write (view and clear an event's waitlist), team:write (list, invite, change and remove team members and assign scanners to gates), privacy:write (export or anonymise everything you hold about a customer), audit:read (read the audit log) and billing:read (your plan, monthly event usage and invoices). The usual API rate limit (100 requests per minute) also applies to MCP calls.
Set it up
claude.ai and Claude Desktop
- Open Settings → Connectors (claude.ai) or Settings → Connectors → Add custom connector (Claude Desktop) and choose Add custom connector.
- Give it a name such as Cleartix and enter
https://cleartix.io/api/mcpas the URL. Leave the OAuth client ID and secret empty, Cleartix registers the connector automatically. - Click Connect. A Cleartix window opens: sign in if you are not already, pick the organisation the assistant may work in and tick the scopes you want to grant, then Approve.
- Back in Claude, enable the connector for your chat and ask, for example, "Which of my events still need work before they can be published?".
Access lasts as long as you keep using it; after 30 days without use the assistant asks you to sign in again. You can end it at any time under Revoke access.
ChatGPT
In ChatGPT, open Settings → Connectors → Create (developer mode), enter https://cleartix.io/api/mcp as the MCP server URL, choose OAuth as authentication and save. The same Cleartix sign-in and consent screen appears; approve it and the connector is ready to use in your chats.
Claude Code
Claude Code can sign in the same way, just add the server without a header and run /mcp to log in:
claude mcp add --transport http cleartix https://cleartix.io/api/mcp
If you prefer a fixed credential (for example in CI or a shared machine), pass an API key as a header instead:
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?".
Cursor and other clients
Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects). Cursor can sign in with OAuth when you leave the headers out; add the headers block to use an API key instead:
{
"mcpServers": {
"cleartix": {
"url": "https://cleartix.io/api/mcp",
"headers": { "Authorization": "Bearer ctk_live_…" }
}
}
}
Other clients that support Streamable HTTP MCP servers can be configured the same way: URL plus, when they cannot sign in, the Authorization header. Clients that only speak stdio can use a bridge such as mcp-remote.
What the assistant can do
Each tool needs the matching scope, the ones you ticked on the consent screen or gave to the API key; tools you have not granted simply are not available to the assistant. All actions are limited to the organisation you approved, and every change is recorded in the audit log with the assistant or key that made it.
- Events:
list_events,get_event,create_event,update_event,publish_event,unpublish_event(takes an event off sale again, as long as nobody has ordered),check_event_readiness,cancel_event,delete_event,get_upload_url(the assistant fetches a short-lived upload URL, uploads the image itself and then sets it on the event or template) - Ticket types & dates:
list_ticket_types,create_ticket_type,update_ticket_type,delete_ticket_type,reorder_ticket_types,set_event_dates(replaces the full list of dates) - Access codes, add-ons, capacity pools & gates:
list_/create_/update_/delete_access_code(s),…_addon(s),…_capacity_pool(s),…_gate(s),get_live_gate_counts - Discount codes:
list_discount_codes(all codes, or only those usable on one event),get_discount_code,create_discount_code,update_discount_code(also switches a code on or off),delete_discount_code, see Discount codes - Event emails:
list_event_emails,set_event_email,preview_event_email,send_event_email - Ticket layout (Studio/Pro):
get_ticket_layout,set_ticket_layout,get_event_ticket_layout,set_event_ticket_layout(sponsors or ads in the bottom third of PDF tickets, see Sponsors and ads on your tickets) - Templates:
list_templates,get_template,create_template,update_template,delete_template,schedule_from_template(withdryRun: trueit only shows the planned dates and the monthly cap check, without creating anything),apply_template,save_event_as_template - Orders & sales:
list_orders(filter by event, status, payment method, buyer e-mail, free text or date range),get_order(including the bank message or invoice number the buyer has to pay with),get_event_sales(tickets sold, check-ins and revenue per ticket type, without attendee data),refund_order,cancel_order(only for online payments still open) - Reconciling bank transfers:
match_bank_transactions(matches the incoming payments of a bank statement, transcribed from a screenshot, PDF or CSV export, to the orders waiting for a bank transfer or invoice payment and proposes an order per line, without booking anything),mark_orders_paid(books up to 50 approved orders as paid in one go and sends the tickets),mark_order_paid(a single order). See Booking wire transfers. - Attendees & tickets:
list_attendees,find_tickets(support lookup by e-mail, name, ticket or order ID across all events),resend_ticket(regenerates the tickets and e-mails the confirmation to the buyer again) - Guest tickets & transfers:
issue_guest_tickets(free tickets for press, sponsors, VIPs or volunteers, a €0 order that consumes capacity like a sale and e-mails the tickets),update_ticket_holder(edits the attendee data on a ticket),transfer_ticket(hands a ticket to someone else: new QR code, the recipient gets a link to accept it) - Check-in:
get_ticket_status(whether a ticket can be scanned, plus its scan history),check_in_ticket,undo_check_in - Privacy (GDPR):
export_customer_data(everything you hold about an e-mail address, for an access request),anonymize_customer(irreversibly erases the person's identity from orders, tickets, passes and consents, for an erasure request) - Waitlist:
list_waitlist,remove_waitlist_entry - Team & scanners:
list_team,invite_member,update_member_role,remove_member,revoke_invite,resend_invite,assign_scanner_to_gate,unassign_scanner_from_gate - Audit & billing:
list_audit_log(who changed what and when, including what assistants and API integrations changed),get_billing_status(your plan, the monthly event cap and how much of it is used),list_invoices - Shop (Studio/Pro):
list_products,create_product,update_product,delete_product,add_product_image,remove_product_image,list_shipping_methods,create_shipping_method,update_shipping_method,delete_shipping_method,list_shipments,mark_order_shipped,get_product_sales,get_product,reorder_products,reorder_product_images,get_product_file_upload_url,attach_product_file,list_product_categories,create_product_category,update_product_category,delete_product_category,reorder_product_categories,get_shop_settings,update_shop_settings,set_shop_header_image, covering product categories, the order of the catalogue and the shop settings (open or closed, texts, category layout, header image); widgets, including shop widgets, vialist_widgets,get_widget,create_widget,update_widget,delete_widget - Locations:
list_locations,create_location - Images:
import_image(Cleartix downloads a public image URL and stores it, for the header image or forimagenodes inside the description, withwidthandalignfor the layout),get_upload_url - Starter kits:
list_starter_kits,create_event_from_starter_kit - Help for the assistant:
describe_event_optionsexplains 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, send_event_email, refund_order, cancel_order, mark_order_paid, mark_orders_paid, undo_check_in, issue_guest_tickets, transfer_ticket, anonymize_customer, remove_waitlist_entry and remove_member, require explicit confirmation: the assistant has to ask you first and pass confirm: true, so a vague request can never cancel an event, refund money or mail your attendees by accident. Refunds are recorded in the name of the person who requested them, so refund_order only works when the assistant signed in through the connector (OAuth); with a plain API key the refund is refused and you handle it in the dashboard. 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."
- "Has order 1234 been paid? Resend the tickets to the buyer."
- "How many tickets did the quiz night sell per type?"
- "Here's a screenshot of my bank statement: book the bank transfers, but show me what you want to book first."
- "Check in the ticket of Jan Peeters at the door."
- "Give the 3 sponsors on this list a free VIP ticket each and send them."
- "Export everything we hold about jan@example.be for a GDPR request."
Whatever the assistant proposes, it only takes effect once the tool runs. You can always ask it to show the plan first.
Stay safe
- Prefer read scopes. Give the assistant a write scope only for the task at hand; you can revoke the grant (or delete the key) afterwards.
- 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.
- Revoke access you no longer use, and rotate an API key immediately if it ends up in a chat log, screenshot or shared config file. The audit log shows exactly what an assistant did.
- Never paste an API key into a prompt: sign in through the connector, or put the key in the client configuration as shown above.
Revoke access
Every assistant that signed in through the connector flow is listed under Settings → API → Connected AI assistants, with the person who granted it, its scopes and when it was last used. Click Revoke to end its access immediately, the assistant will have to sign in and be approved again. Grants also appear in the audit log, both when they are approved and when they are revoked.
Assistants that use an API key are managed under Settings → API keys: delete or rotate the key there.
Note: MCP is available on every plan and uses the same scopes and rate limit as the REST API (which itself requires Studio or Pro). Hosted assistants (claude.ai, Claude Desktop, ChatGPT) sign in with your Cleartix account; command-line tools can still use an API key as the Authorization header.
Last updated: November 11, 2026