Ticketsauce MCP by usefulapi

io.usefulapi/ticketsauce

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

Yes, your AI can use this right now.Answered a live MCP handshake in 341 ms with no sign-in needed and exposes 5 tools.
Is this your server? Claim the listing. Verified adds a vendor-confirmed mark on this page and matching app pages.
Claim with Verified — $49/moWant it in front of people comparing E-commerce tools? Feature it — $149/mo

Connect it

Settings → Connectors → Add custom connector
URL: https://ticketsauce.usefulapi.io/mcp

5 tools, pulled live

Pulled straight from the server with tools/list on 2026-10-27.
ticketsauce_list_eventsread-only

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/e

ticketsauce_get_eventread-only

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_ordersread-only

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, q

ticketsauce_get_orderread-only

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_idsread-only

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}.

Alternatives in E-commerce

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”