# Ticketsauce Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Ticketsauce

Check your Ticketsauce events, orders, and ticket check-ins

- Record: https://musedirectory.ai/connector/ticketsauce
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/ticketsauce/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 16ms, checked 2026-10-30T00:36:14Z
- Endpoint: https://ticketsauce.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-30T00:36:14Z)
- Source: Found in the official MCP Registry (io.usefulapi/ticketsauce) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fticketsauce

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.

Example request: "Show me all my events this weekend and how many tickets have sold for each one."

How to connect: Not 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.

Tools:
- 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_
- 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 orde
- 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}.

Screening checks:
- MCP handshake: pass (Answered in 16ms)
- Domain against threat feeds (Cloudflare security DNS): pass (ticketsauce.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (5 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)