Integration

TicketSource integration

TicketSource is a UK online box office for selling event tickets. Read your events with their venues and performance dates, read the bookings of a date or of a customer with their payment lines and booked seats or places, and list, create, update and delete customers and the notes kept against them; lists filter by creation and update date, and events and dates by their own fields. Creating events, dates or bookings is not offered by the API. Authentication is the API key from Settings > API in TicketSource, sent as a bearer token in the Authorization header.

Connect TicketSource How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with TicketSource

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.

Customer, 5 operations

create_customerCreate customerPOSTCreates a customer record and returns it. Every attribute is optional but at least one must be given: names, address, telephone, e-mail, membership (identifier, start and end dates) and contact consent.
delete_customerDelete customerDELETEDeletes a customer record. TicketSource answers with an empty body (204 No Content).
get_customerGet customerGETReturns one customer: names, address, telephone, e-mail, membership identifier and dates, contact consent, and links to their bookings and notes.
list_customersList customersGETLists your customers in pages: names, address, telephone, e-mail, membership and contact consent. Filters on created_at and updated_at.
update_customerUpdate customerPATCHUpdates a customer: send only the attributes to change (names, address, telephone, e-mail, membership, consent). resource_id must repeat CustomerId. Returns the updated record.

Note, 4 operations

create_customer_noteCreate customer notePOSTAdds a note to a customer and returns it. Both the note text (description) and its author label (created_by) are required.
delete_customer_noteDelete customer noteDELETEDeletes a note from a customer. TicketSource answers with an empty body (204 No Content).
get_customer_noteGet customer noteGETReturns one note of a customer: text, who or what created it, and creation and update times.
list_customer_notesList customer notesGETLists the notes kept against a customer: text, who or what created it, and creation and update times.

Booking, 3 operations

get_bookingGet bookingGETReturns one booking: its reference, payment lines with amounts, discounts, refunds and gift aid, contact consent, who booked it, and links to its seats, customer and date.
list_customer_bookingsList customer bookingsGETLists a customer's bookings: booking reference, payment lines (tickets, donations, sundries) with gross, fee, VAT, discounts and net amounts, refunds, consent and who booked. Filters on created_at and updated_at.
list_date_bookingsList date bookingsGETLists the bookings of a date (performance): booking reference, payment lines (tickets, donations, sundries) with gross, fee, VAT, discounts and net amounts, refunds, consent and who booked. Filters on created_at and updated_at.

Date, 3 operations

get_dateGet dateGETReturns one date (performance): doors open, start and end times (ISO 8601, UTC), sale window, on-sale, public and cancelled flags, and links to its event, venue, bookings and public booking page.
list_event_datesList event datesGETLists the dates (performances) of an event: doors open, start and end times, sale window, on-sale, public and cancelled flags, and the public booking URL. Filters on start, created_at and updated_at.
list_venue_datesList venue datesGETLists the dates (performances) held at a venue: doors open, start and end times, sale window, on-sale, public and cancelled flags, and the public booking URL. Filters on start, created_at and updated_at.

Event, 2 operations

get_eventGet eventGETReturns one event: name, reference, HTML description, comment, keywords, terms, category, genre, images, third-party consent settings and the activated, archived and public flags.
list_eventsList eventsGETLists your events in pages (name, reference, description, category, genre, images, status flags). By default only events not yet settled are returned; set the settled filter operator to any for all.

Seat, 2 operations

get_seatGet seatGETReturns one seat or place of a booking: row and seat reference, price category, booked and cancelled flags, and the attendee's name, company, telephone and e-mail.
list_booking_seatsList booking seatsGETLists the seats or places of a booking: row and seat reference (if allocated), price category, booked and cancelled flags, and the attendee's name, company, telephone and e-mail.

Venue, 2 operations

get_venueGet venueGETReturns one venue of an event: name, address and box office telephone and e-mail.
list_event_venuesList event venuesGETLists the venues of an event, each with its name, address and box office telephone and e-mail.

Use TicketSource from Claude Code, Cursor or Codex

Connect TicketSource in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TicketSource 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 TicketSource

Create your workspace
Sign up free. Nothing to install.
Connect TicketSource once
Add your TicketSource 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.