Integration

Event Tickets integration

Event Tickets is The Events Calendar's WordPress plugin for RSVPs and ticket sales (with WooCommerce, Easy Digital Downloads or Tickets Commerce). This read-only integration lists and reads a site's tickets (price, capacity, sales window, availability, check-in and RSVP counts) and its attendees (name, email, order, ticket, check-in status and payment amount), with filters by event post, ticket, status and date. Creating or editing tickets, carts, check-in and attendee registration answers (custom fields) are not exposed. Every site is its own host: give the site's domain. Authentication is WordPress HTTP Basic with a username and an Application Password (WordPress admin, Users, Profile, Application Passwords); attendee data is returned only to a user allowed to see it; without such a user, attendee lists come back empty, a single attendee is refused, and tickets come back without their check-in and RSVP counts.

Connect Event Tickets How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Event Tickets

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.

Attendee, 2 operations

get_attendeeGet attendeeGETReturns one attendee: name, email, event post and ticket, order number, SKU, check-in status and details, RSVP answer and payment. Needs a user allowed to see attendees.
list_attendeesList attendeesGETLists a site's attendees (ticket holders and RSVPs) with name, email, ticket, order, check-in and payment amount. Needs a user allowed to see attendees. Filter by event post, ticket, check-in or RSVP status, name or email.

Ticket, 2 operations

get_ticketGet ticketGETReturns one ticket or RSVP: event post, provider, price, capacity and stock, sales window, availability and, for an authorized user, check-in and RSVP counts.
list_ticketsList ticketsGETLists a site's tickets and RSVPs with price, capacity, sales window, availability and, for an authorized user, check-in and RSVP counts. Filter by event post, availability, provider or dates; page with page and per_page.

Use Event Tickets from Claude Code, Cursor or Codex

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

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