Spektrix MCP by usefulapi is an MCP server published by io.usefulapi, hosted at spektrix.usefulapi.io. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including spektrix_list_events, spektrix_list_event_instances, spektrix_list_instances, spektrix_list_memberships, spektrix_list_order_changes.
Read events, performances, memberships and order changes in Spektrix.
4,207 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
List the events (shows) of the Spektrix system, with their descriptions, durations and attributes. Filter by name, on-sale status or a date range of instances (performances). Use a short date range. Spektrix API: GET /api/v3/events.
| Parameter | Type | Description |
|---|---|---|
| name | string | Filter by event name. |
| on_sale | boolean | true = only events on sale; false = only events not on sale. |
| instance_start_to | string | Last performance date to include, YYYY-MM-DD. |
| instance_start_from | string | First performance date to include, YYYY-MM-DD. |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
{
"name": "spektrix_list_events",
"title": "List events",
"description": "List the events (shows) of the Spektrix system, with their descriptions, durations and attributes. Filter by name, on-sale status or a date range of instances (performances). Use a short date range. Spektrix API: GET /api/v3/events.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"name": {
"type": "string",
"description": "Filter by event name."
},
"on_sale": {
"type": "boolean",
"description": "true = only events on sale; false = only events not on sale."
},
"instance_start_to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last performance date to include, YYYY-MM-DD."
},
"instance_start_from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First performance date to include, YYYY-MM-DD."
}
}
},
"annotations": {
"title": "List events",
"readOnlyHint": true
}
}List the performances (instances) of one event between two dates, with their start times and on-sale status. Get the event id from spektrix_list_events. Spektrix API: GET /api/v3/events/{id}/instances.
| Parameter | Type | Description |
|---|---|---|
| event_id * | string | A Spektrix id. |
| start_to | string | Last performance date, YYYY-MM-DD. |
| start_from | string | First performance date, YYYY-MM-DD. |
{
"name": "spektrix_list_event_instances",
"title": "List performances of an event",
"description": "List the performances (instances) of one event between two dates, with their start times and on-sale status. Get the event id from spektrix_list_events. Spektrix API: GET /api/v3/events/{id}/instances.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id"
],
"properties": {
"event_id": {
"type": "string",
"pattern": "^[A-Za-z0-9-]{1,80}$",
"description": "A Spektrix id."
},
"start_to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last performance date, YYYY-MM-DD."
},
"start_from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First performance date, YYYY-MM-DD."
}
}
},
"annotations": {
"title": "List performances of an event",
"readOnlyHint": true
}
}List performances (instances) across all events for a date range, optionally for one event name. Use a short date range; the vendor recommends small date batches. Spektrix API: GET /api/v3/instances.
| Parameter | Type | Description |
|---|---|---|
| start_to | string | Last performance date, YYYY-MM-DD. |
| event_name | string | Only performances of this event name. |
| start_from | string | First performance date, YYYY-MM-DD. |
{
"name": "spektrix_list_instances",
"title": "List performances",
"description": "List performances (instances) across all events for a date range, optionally for one event name. Use a short date range; the vendor recommends small date batches. Spektrix API: GET /api/v3/instances.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"start_to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Last performance date, YYYY-MM-DD."
},
"event_name": {
"type": "string",
"description": "Only performances of this event name."
},
"start_from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First performance date, YYYY-MM-DD."
}
}
},
"annotations": {
"title": "List performances",
"readOnlyHint": true
}
}List the memberships this Spektrix system sells (id, name and description). Spektrix API: GET /api/v3/memberships.
No parameters.
{
"name": "spektrix_list_memberships",
"title": "List memberships",
"description": "List the memberships this Spektrix system sells (id, name and description). Spektrix API: GET /api/v3/memberships.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List memberships",
"readOnlyHint": true
}
}List confirmed orders modified since a time, oldest first, up to 100 per page (customer id, tickets, seats, performances and totals). To read the next page, pass the since value from paging.next. The orders sync endpoint is Early Access: an error may mean the vendor has not enabled it for this system. Spektrix API: GET /api/v3/orders/sync.
| Parameter | Type | Description |
|---|---|---|
| since * | string | Return orders modified on or after this instant (ISO-8601 date-time, UTC). |
{
"name": "spektrix_list_order_changes",
"title": "List order changes",
"description": "List confirmed orders modified since a time, oldest first, up to 100 per page (customer id, tickets, seats, performances and totals). To read the next page, pass the since value from paging.next. The orders sync endpoint is Early Access: an error may mean the vendor has not enabled it for this system. Spektrix API: GET /api/v3/orders/sync.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"since"
],
"properties": {
"since": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(:\\d{2}(\\.\\d+)?)?(Z|[+-]\\d{2}:\\d{2})?$",
"description": "Return orders modified on or after this instant (ISO-8601 date-time, UTC)."
}
}
},
"annotations": {
"title": "List order changes",
"readOnlyHint": true
}
}Tools for Spektrix, hosted by usefulapi.io. If the user is new or asks what this server can do, suggest requests such as: "Which events are on sale at our theatre in the next 30 days?"; "List the performances of the spring season event for next month."; "Show the orders changed since yesterday morning, with their performances and totals.". Read-only tools never change data; ask the user before a tool that creates, changes or deletes Spektrix data. Free plan: 50 tool calls per month. Run spektrix_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run spektrix_request_feature to record the request. Paid plans: Pro (10,000 tool calls a month, $9/month or $90/year, for normal use) and Pro+ (100,000 tool calls a month, $39/month or $390/year, for automations and heavy use). A plan can be cancelled at any time and then runs to the end of the paid period, so it also suits a one-time job. When the user wants more calls or reaches the limit, run spektrix_upgrade without a plan: it returns both plans, each with a payment link for the user to open. spektrix_cancel_subscription cancels Pro at the end of the paid period.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.