Eventually Ticketing
Integrations

MCP event data reference

The customer MCP server exposes event data to AI assistants connected to your account. The get_event tool returns an event's details, including its ticket types, and each ticket type carries a sku and a generatedSku field. Event data is read-only.

Accessing event data

Connect an AI assistant to your Eventually account, then use the get_event tool to read event data. Event data is included by default in the assistant connection. See Connect Claude or ChatGPT to your account to set up the connection.

The sku and generatedSku fields

Each ticket type in the get_event response includes two SKU fields:

  • sku is the SKU the Squarespace store carries for the ticket's variant.

  • generatedSku is the SKU Eventually automatically generated for the ticket type. When sku equals generatedSku, no custom SKU is set on the tier.

Series results in list_events

For upcoming, drafts, series, and all results, each series appears once. Past results include each completed session of a recurring series, so a series can appear once per date. Two fields describe how a result relates to its series:

  • isRecurring indicates whether the date belongs to a series.

  • isSeriesRoot marks the date that represents its series in the list.

The event summaries returned by get_event and search_events use the same series membership and representative-date semantics.

Location fields in event summaries

Every event summary carries locationType, which identifies the event's location type, so an assistant can tell a virtual event from one with a physical venue. The place fields follow that type:

  • In-person and hybrid summaries carry location and venueName as before.

  • A virtual summary omits its stored venue details, so an event that switched from in person to virtual stops reporting its old venue.

  • If the virtual event has a join link set as its location, the link stays in location.

Was this helpful?
Was this helpful?