Integration

Ticketsauce integration

Ticketsauce is an event ticketing platform. An agent can list the events an account owns (filtered by partner, organization, dates, status and privacy), read one event by id or slug with its description, order and ticket counts, list an event's orders with buyer details, amounts and fees (optionally with tickets and questionnaire answers), and read one order with its tickets. The API is read-only and its answers are cached by Ticketsauce for up to an hour. The ticket check-in id listing is not exposed because its response is undocumented. Authentication uses a client_id and client_secret generated on the Ticketsauce platform, exchanged for short-lived access tokens with the OAuth2 client credentials grant.

Connect Ticketsauce How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ticketsauce.Built from the 4 Ticketsauce tools below, on the connection you add once.

What you can do with Ticketsauce

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Event, 2 operations

get_eventGet eventGETReturns one event by id or slug: dates, venue, status, summary and description (plain and HTML), order and ticket counts, URLs and logo. Cached for 1 hour.
list_eventsList eventsGETLists events you own, filterable by partner, organization, start, end and creation dates, status and privacy, sorted by date, name or city. All dates are UTC. Cached for 1 hour.

Order, 2 operations

get_orderGet orderGETReturns one order (buyer, amounts, fees, promo code, payment date, delivery method) with its tickets. Cached for 1 hour, so it may not mirror the latest changes.
list_ordersList ordersGETLists an event's orders (buyer, amounts, fees, promo code, payment date), paged, filterable by order or modification date, buyer email or last name, total and promo use. Dates are UTC; cached 1 hour.

Use Ticketsauce from Claude Code, Cursor or Codex

Connect Ticketsauce in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ticketsauce operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Ticketsauce

Create your workspace
Sign up free. Nothing to install.
Connect Ticketsauce once
Add your Ticketsauce connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.