Check your Ticketsauce events, orders, and ticket check-ins
Read-only access to Ticketsauce event ticketing data. View your events, customer orders with buyer details and totals, and ticket check-in IDs for door reconciliation. Requires Ticketsauce account.
Try asking Muse: "Show me all my events this weekend and how many tickets have sold for each one."
Source: Found in the official MCP Registry (io.usefulapi/ticketsauce) · First listed October 30, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://ticketsauce.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Ticketsauce is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://ticketsauce.usefulapi.io/mcpResponse time at the last check: 16ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
ticketsauce_list_eventsList 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_ticketsauce_get_eventOne 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_ordersOrders 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 ordeticketsauce_get_orderOne 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_idsThe 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}.https://ticketsauce.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Ticketsauce to help me. It is a free service with an MCP server at https://ticketsauce.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 30, 2026, 00:36 UTC) the endpoint was working, answering in 16ms. It is checked every 15 minutes.
It was screened on October 30, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 5 tools, including ticketsauce_list_events, ticketsauce_get_event, ticketsauce_list_orders, ticketsauce_get_order. For example, you could ask Muse: "Show me all my events this weekend and how many tickets have sold for each one."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/ticketsauce)). If you build Ticketsauce, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/ticketsauce"><img src="https://musedirectory.ai/badge/ticketsauce.svg" alt="Ticketsauce on musedirectory.ai" width="236" height="40"></a>