Read Ticketsauce events, orders and ticket check-in IDs (read-only). For event organizers who sell tickets with Ticketsauce and want answers about events, orders and check-ins. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"ticketsauce": {
"url": "https://ticketsauce.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"ticketsauce": {
"type": "http",
"url": "https://ticketsauce.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The AI lists your events with dates, venue, timezone and whether tickets are on sale, and opens one event to show how many tickets have been sold.
ticketsauce_list_events ticketsauce_get_event
The AI lists the orders of one event placed in a time window, newest first, with totals, promo codes and ticket counts. Order replies are cached for up to an hour.
ticketsauce_list_events ticketsauce_list_orders
The AI looks up an order by buyer email or last name and shows the buyer details, totals and each ticket with its type and redeemed state.
ticketsauce_list_orders ticketsauce_get_order
The AI lists the orders of an event that used a promo code or exceed a set amount, and sums the totals, refunds and fees for each group.
ticketsauce_list_orders
The AI retrieves the check-in IDs of an event (cached 5 minutes) and the orders with ticket redeemed states (cached up to an hour), so you can reconcile the door count. The two can lag the live door.
ticketsauce_list_checkin_ids ticketsauce_list_orders
The login page asks for your Client ID and Client Secret.
Log in to Ticketsauce, hover My Account (top right), click API, and copy the Client ID and Client Secret (click Generate API Keys if the secret is not shown). They are used only to call the Ticketsauce API on your behalf; they are never shown to anyone. The API only reads: this server cannot change your events or orders.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Ticketsauce connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
ticketsauce_list_events | read | List events List the events you own on Ticketsauce with id, name, slug, start/end (local and UTC), venue address, timezone, organization, privacy type, whether tickets are on sale, and the event and ticket-shop URLs. Filter by start/end/created dates (yyyy-mm-dd, UTC), a phrase such as this_weekend, organization or partner. The API has no paging for events. Use the event id for orders and check-ins. GET /v2/events. |
ticketsauce_get_event | read | Get event One event by id or slug: everything in the list plus summary and description (text and HTML), order_count and ticket_count (tickets sold, not refunded or voided). Replies are cached for an hour. GET /v2/event/{id_or_slug}. |
ticketsauce_list_orders | read | List orders of an event Orders of one event, oldest first by default (pass sort_dir desc for newest first): order id, status, buyer name, email, phone and address, totals (total_paid, refund_amount, taxes, fees), promo code, ticket_count, paid date. Contains your customers' personal data. Filter by order or modified dates, a phrase, buyer email or last name (exact match), totals, or promo use; optionally embed tickets, questionnaire answers and line-item fees. Paged: per_page up to 500, then pass next_page. Replies are cached for an hour. GET /v2/orders/{event_id}. |
ticketsauce_get_order | read | Get order One order by id, with its buyer details, totals and its tickets (ticket type, name, price, redeemed state, promo code). Contains personal data. Replies are cached for an hour. GET /v2/order/{order_id}. |
ticketsauce_list_checkin_ids | read | List ticket check-in ids The ticket check-in ids of one event, for door/scanning reconciliation (the API documents no response fields; the reply is returned as is). Paged: per_page up to 5000, then pass next_page. Replies are cached for 5 minutes. GET /v2/tickets/checkin_ids/{event_id}. |
ticketsauce_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
ticketsauce_request_feature | Request a missing feature Tell usefulapi that the user needs something the Ticketsauce tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
ticketsauce_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Ticketsauce (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
ticketsauce_cancel_subscription | Cancel the Pro subscription Cancel the caller's Ticketsauce Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run ticketsauce_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Ticketsauce server only. Subscribe with ticketsauce_upgrade (it returns a Stripe Checkout link). Cancel any time with ticketsauce_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running ticketsauce_upgrade before then undoes the cancel. Or write to [email protected].
Review the events you are running. Review recent orders for an event. Find a buyer's order and tickets. Audit promo code use. Pull check-in IDs for door reconciliation. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Ticketsauce. The server calls the Ticketsauce API with your own Ticketsauce access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Client ID and Client Secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Ticketsauce API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Ticketsauce.
All 5 Ticketsauce tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Ticketsauce server only. Cancel any time: Pro then runs to the end of the paid period. Run ticketsauce_usage_status to see how many calls you used.
Ask the AI to run ticketsauce_upgrade: it returns a Stripe Checkout link. To cancel, run ticketsauce_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with ticketsauce_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.