AI Assistant (MCP)

The MCP server lets you connect AI assistants — Claude, Cursor, and any other tool that supports the Model Context Protocol — directly to your Quicket organization. Once connected, you can ask the assistant questions in plain language and it reads your live event data to answer:

• "Which of my events is selling slowest this week?"
• "Summarize check-in and attendance for Summer Fest."
• "Break down revenue by ticket category for my last event."
• "How many complimentary tickets have I issued across all events?"

Each connection uses one organization API key, so the assistant only ever sees that organization's data, and every action is read-only — the assistant can look, but it cannot change anything, issue refunds, or email attendees.

This complements the Integrations API (for CRMs, warehouses, and custom code) — the MCP server is the same data, exposed for conversational AI instead of scripts.

Where to manage keys

The MCP server authenticates with the same API keys as the Integrations API. Organization admins create and revoke them in the dashboard:

• Location: Organization dashboard → Settings → API keys section
• Path: /organizations/<org-slug>/settings

The full secret (qkt_live_...) is shown once at creation. Copy it, then paste it into your AI client's configuration.

:::warning Treat the key like a password Anyone with the key can read your organization's event and attendee data through any AI assistant. Store it securely, and revoke it in Settings the moment it is no longer needed. :::

Connecting Claude (or another MCP client)

Point your client at the MCP endpoint and pass the key as a bearer token.

Endpoint

https://api.quicket.me/v2/mcp

Example client configuration (remote MCP server with an auth header):

{
  "mcpServers": {
    "quicket": {
      "url": "https://api.quicket.me/v2/mcp",
      "headers": {
        "Authorization": "Bearer qkt_live_<prefix>_<secret>"
      }
    }
  }
}

Exact steps vary by client — check your assistant's documentation for "custom / remote MCP server." After connecting, the Quicket tools appear in the assistant and it will call them automatically when you ask about your events.

What the assistant can do

The assistant has read-only tools covering the same areas as your dashboard, including:

• Organization overview — event count, team, total ticket revenue
• Events — list and search your events, per-event sales and status
• Analytics — sales trends, conversion, traffic sources
• Attendance — check-in and gate summaries
• Finance — revenue and payout-related summaries
• Categories, coupons, and operations — ticket tiers, discount usage, event operations snapshots

It cannot create or edit events, change prices, issue refunds, message attendees, or manage members. Those remain in the dashboard.

Privacy and security

• The assistant can read personal data (attendee names, emails, phones) where a tool exposes it. Sensitive payment internals are redacted, but treat the conversation as containing attendee data and handle it under your privacy policy and applicable law.
• Data is sent to your AI provider (e.g. Anthropic for Claude) when the assistant makes a tool call. Review that provider's data-handling terms before connecting.
• Use one key per assistant/integration so you can revoke a single connection without disrupting others.
• Requests are rate-limited per key; a burst of questions may briefly slow down.

Related docs

• Integrations API — script/CRM access to the same data (REST)
• Organization Settings — where API keys are managed
• Event Analytics — the dashboard views the assistant summarizes
• Attendee Insights — cross-event audience CRM