Read Ticketsauce events, orders and ticket check-in IDs (read-only). Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the Ticketsauce connector, then ask in plain words. The AI picks the tools.
For event organizers who sell tickets with Ticketsauce and want answers about events, orders and check-ins.
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.
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.
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.
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.
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.
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.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
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"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper account | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per account | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Ticketsauce server only. Ask your AI to run ticketsauce_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with ticketsauce_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with ticketsauce_upgrade before then undoes the cancel. Or write to [email protected].
ticketsauce_list_eventsticketsauce_get_eventticketsauce_list_ordersticketsauce_get_orderticketsauce_list_checkin_idsticketsauce_usage_statusticketsauce_request_featureticketsauce_upgradeticketsauce_cancel_subscriptionReview 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 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Ticketsauce server only. Cancel any time: your paid plan 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 and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run ticketsauce_cancel_subscription. Your paid plan 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.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.