Ticketsauce MCP by usefulapi

io.usefulapi/ticketsauce · v1.0.0 · ecommerce

Ticketsauce MCP by usefulapi is healthy: it completed an MCP handshake in 1168 ms and exposes 5 tools.

Read Ticketsauce events, orders and ticket check-in IDs (read-only).

Endpoint: https://ticketsauce.usefulapi.io/mcp (streamable-http)

Facts

Checked (UTC)	Status	Latency	Error
2026-10-26T06:00:18.956Z	Healthy	1168
2026-10-26T06:00:18.557Z	Healthy	880

`ticketsauce_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, organizatio
`ticketsauce_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`	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,
`ticketsauce_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`	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}.