# How to connect Ticket Tailor MCP to Claude Cowork

```json
{
  "title": "How to connect Ticket Tailor MCP to Claude Cowork",
  "toolkit": "Ticket Tailor MCP",
  "toolkit_slug": "ticket_tailor_mcp",
  "framework": "Claude Cowork",
  "framework_slug": "claude-cowork",
  "url": "https://composio.dev/toolkits/ticket_tailor_mcp/framework/claude-cowork",
  "markdown_url": "https://composio.dev/toolkits/ticket_tailor_mcp/framework/claude-cowork.md",
  "updated_at": "2026-09-07T05:39:21.529Z"
}
```

## Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.
This guide walks you through the easiest and most secure way to connect your Ticket Tailor account to Cowork via Composio Connect, enabling it to list upcoming events and ticket counts, create VIP ticket type for Main Stage, check in attendee by order number, and more such actions on your behalf without compromising your account security.

## Also integrate Ticket Tailor MCP with

- [ChatGPT Work](https://composio.dev/toolkits/ticket_tailor_mcp/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/ticket_tailor_mcp/framework/hermes-agent)

## Connect Ticket Tailor MCP to Claude Cowork

### Connecting Ticket Tailor to Claude Cowork
1. Open Customize
In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.
2. Add the Composio MCP server
Click Add custom connector and paste in the Composio MCP server URL:

```bash
https://connect.composio.dev/mcp
```

## What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.
With Composio Connect, Cowork can securely access apps like Ticket Tailor through MCP without you sharing account credentials directly with the agent.

## What is the Ticket Tailor MCP server, and what's possible with it?

The Ticket Tailor MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ticket Tailor account. It provides structured and secure access so your agent can perform Ticket Tailor operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `TICKET_TAILOR_MCP_BUNDLE_CREATE` | Bundle create | Creates a new bundle in event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_BUNDLE_DELETE` | Bundle delete | Delete a bundle. This action is irreversible. The bundle will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_BUNDLE_UPDATE` | Bundle update | Updates an existing bundle in event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_CHECK_IN_CREATE` | Check in create | Creates a check-in or check-out record for an issued ticket. Check-ins track when attendees arrive at or leave an event. This is essential for event management, attendance tracking, and security. You can check in attendees at the door, track early departures, or manage re-entry. The system prevents duplicate check-ins unless explicitly allowed. These records stack up, so the current check-in state of an issued ticket is the sum of its corresponding records. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_CHECK_INS_GET` | Check ins get | Returns a list of check-ins. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_CHECKOUT_FORM_ELEMENT_BY_ID_GET` | Checkout form element by id get | Returns a checkout form element by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_CHECKOUT_FORM_ELEMENTS_GET` | Checkout form elements get | Returns a list of checkout form elements. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_CHECKOUT_FORM_ELEMENT_UPDATE` | Checkout form element update | Updates an existing checkout form element. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_CHECKOUT_FORMS_GET` | Checkout forms get | Returns a list of checkout forms. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_DISCOUNT_BY_ID_GET` | Discount by id get | Returns a discount by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_DISCOUNT_CREATE` | Discount create | Creates a discount code that customers can use during checkout to receive reduced pricing. Discount codes are powerful marketing tools that can increase sales, reward loyal customers, or fill seats. You can create percentage-based or fixed-amount discounts, set usage limits, and restrict them to specific ticket types or products. The discount code will be immediately available for customers to use. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_DISCOUNT_DELETE` | Discount delete | Delete a discount. This action is irreversible. The discount will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_DISCOUNTS_GET` | Discounts get | Returns a list of discounts. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_DISCOUNT_UPDATE` | Discount update | Updates an existing discount. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_BY_ID_GET` | Event by id get | Returns an event by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_MANAGEMENT` | Event management | Create multiple events with single tool call. Create one or more event series. Create one or more event occurrences for one or more new event series. Create one or more event occurrences for one or more existing event series. Create one or more ticket types for one or more new event series. Create one or more ticket types for one or more existing event series. Create one or more ticket groups for one or more new event series. Create one or more ticket groups for one or more existing event series. Pass event series related data in eventSeries array to create event series. Pass event occurrences related data in eventOccurrences array to create event occurrences. Pass ticket types related data in ticketTypes array to create ticket types. Pass ticket groups related data in ticketGroups array to create ticket groups. When creating multiple event series with multiple event occurrences and/or multiple ticket types and or multiple ticket groups, use a placeholder for event_series_id in eventOccurrences and ticketTypes and ticketGroups arrays. Placeholder must have a structure of es_placeholder1, es_placeholder2, etc. where the number is the index of the previously created event series. When creating ticket groups and referencing a ticket type that is to be created in the same call, use a placeholder for ticket_type_ids in ticketGroups array. Placeholder must have a structure of tt_placeholder1, tt_placeholder2, etc. where the number is the index of the previously created ticket type. When creating event occurrences or ticket types or ticket groups for an existing event series, use the id of the event series in the event_series_id field. Try to find existing event series first before creating a new one (by name or venue), unless user is explicitly asking to create a new event series. Do not use this tool to update or delete event series, event occurrences or ticket types or ticket groups. Use separate tools for that. Event occurrence end datetime must be after start datetime. Ticket group can not contain bundle_ids when ticket group has max_quantity, max_per_order or min_per_order populated. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_OCCURRENCE_BY_ID_GET` | Event occurrence by id get | Returns an event occurrence by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_OCCURRENCE_DELETE` | Event occurrence delete | Delete event occurrence, only if there are no associated orders. Otherwise, set it as hidden. This action is irreversible. The event occurrence will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_OCCURRENCES_GET` | Event occurrences get | Returns a list of event occurrences. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_OCCURRENCE_UPDATE` | Event occurrence update | Updates an existing event occurrence. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_SERIES_BY_ID_GET` | Event series by id get | Returns an event series by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_SERIES_DELETE` | Event series delete | Delete an event series and its associated events. This action is irreversible. The event series and its events will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_SERIES_GET` | Event series get | Retrieves a paginated list of event series from your Ticket Tailor account. Event series are collections of related events (like a recurring concert series or festival). Use this to browse, search, and filter your event series by status, name, venue, or creation date. This is a read-only operation that returns metadata about your event series without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_SERIES_STATUS_CHANGE` | Event series status change | Changes the status of an event series (publish, draft, or close sales). Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENT_SERIES_UPDATE` | Event series update | Updates an existing event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_EVENTS_GET` | Events get | Retrieves a paginated list of individual event occurrences from your Ticket Tailor account. Events are specific instances within an event series (typically either for time slot admission; or else individual instances of multi-day events like 'Saturday' or 'Sunday' festival tickets, or 'Workshop Session A'). Use this to browse, search, and filter your events by status, name, venue, or date range. This is a read-only operation that returns metadata about your events without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_HOLD_BY_ID_GET` | Hold by id get | Returns a hold by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_HOLD_CREATE` | Hold create | Creates a new hold. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_HOLD_DELETE` | Hold delete | Delete a hold. This action is irreversible. The hold will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_HOLDS_GET` | Holds get | Returns a list of holds. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_HOLD_UPDATE` | Hold update | Updates an existing hold. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_BY_ID_GET` | Issued membership by id get | Returns an issued membership by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_CREATE` | Issued membership create | Creates a new issued membership for a membership type. An issued membership represents an actual membership given to a person. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_REDEMPTION_CREATE` | Issued membership redemption create | Creates a redemption for an issued membership at a specific event. This records that the issued membership was used for entry to the event. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_MEMBERSHIPS_GET` | Issued memberships get | Returns a paginated list of issued memberships. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_UPDATE` | Issued membership update | Updates an existing issued membership. Only fixed date types are allowed when updating. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_MEMBERSHIP_VOID` | Issued membership void | Voids an existing issued membership. A voided membership cannot be used for redemptions. This action is irreversible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_TICKET_BY_ID_GET` | Issued ticket by id get | Returns an issued ticket by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_TICKET_CREATE` | Issued ticket create | Creates a new issued ticket for an event occurrence from available inventory. Issued tickets represent actual tickets that have been allocated to a specific person and can be used for entry. This tool can create tickets from either existing ticket type inventory or from a hold (reserved tickets). The created ticket will be immediately available for check-in and will be included in ticket counts. Ticket Tailor fees apply to issued tickets created via the Ticket Tailor API, irrespective of whether those tickets are free or paid-for. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_TICKETS_GET` | Issued tickets get | Returns a list of issued tickets. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ISSUED_TICKET_VOID` | Issued ticket void | Voids an issued ticket. This action is irreversible. This will only mark the ticket as voided (no longer valid) and will not cancel an entire order or issue a refund. You can also void an issued ticket to a hold, which will create a hold from the issued ticket and not put the allocation back on sale. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_MEMBERSHIP_PHOTO_SHARE_GET` | Membership photo share get | Returns a temporary signed URL for the issued membership photo. The URL has an expiry time after which it will no longer be accessible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_BY_ID_GET` | Membership type by id get | Returns a membership type by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_CREATE` | Membership type create | Creates a new membership type. Membership types define the configuration for issued memberships including validity periods, redemption limits, and whether photos are required. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_DELETE` | Membership type delete | Deletes a membership type. A membership type can only be deleted if it has no issued memberships and no linked products. This action is irreversible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_MEMBERSHIP_TYPES_GET` | Membership types get | Returns a paginated list of membership types. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_MEMBERSHIP_TYPE_UPDATE` | Membership type update | Updates an existing membership type. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ORDER_BY_ID_GET` | Order by id get | Returns an order by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ORDER_CONFIRM_PAYMENT` | Order confirm payment | Confirm an offline payment has been paid for an order. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ORDERS_GET` | Orders get | Retrieves a paginated list of customer orders from your Ticket Tailor account. Orders represent completed ticket (and/or product) purchases and contain information about the buyer, items purchased, payment status, and order details. Use this to track sales, analyze customer data, and manage order fulfillment. This is a read-only operation that returns order information without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_ORDER_UPDATE` | Order update | Updates an existing order. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_OVERRIDE_CREATE` | Override create | Creates a new override for event series. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_OVERRIDES_GET` | Overrides get | Returns a list of overrides. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_OVERRIDE_UPDATE` | Override update | Update existing override. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_OVERVIEW_GET` | Overview get | Retrieve a comprehensive overview of your Ticket Tailor box office account, including key metrics, account information, and summary statistics. This provides a high-level dashboard view with data about your events, sales, and account status. Useful for getting a quick snapshot of your business performance and account health. This is a read-only operation that returns account summary information without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_PING_GET` | Ping get | Tests connectivity to the Ticket Tailor API server and retrieves version information. This is a lightweight health check that verifies your API credentials are valid and the service is responding. Useful for troubleshooting connection issues, validating API access, or checking service status. Returns server version details and confirms your authentication is working properly. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_PRODUCT_BY_ID_GET` | Product by id get | Returns a product by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_PRODUCT_CREATE` | Product create | Creates a new product that can be sold alongside tickets. Products are additional items like merchandise, parking passes, meal vouchers, or special add-ons that customers can purchase during the ticket buying process. Products can be linked to specific event series or made available across all events, or sold via a standalone store (not yet available through the API). They can have their own pricing, inventory limits, and delivery instructions. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_PRODUCT_DELETE` | Product delete | Delete a product. This action is irreversible. The product will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_PRODUCTS_GET` | Products get | Returns a list of products. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_PRODUCT_UPDATE` | Product update | Updates an existing product. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_STORE_GET` | Store get | Retrieves the current store configuration including store ID, currency, name, payment methods, and associated products. This provides comprehensive information about your Ticket Tailor store setup and configuration. Useful for understanding your store's current settings and associated resources. This is a read-only operation that returns store information without modifying any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_STORE_LIST` | Store list | Retrieves a list of all stores associated with the provided API key. This tool is useful for managing multiple stores within your Ticket Tailor account. It returns a list of store IDs, names, and other relevant details for each store. This is a read-only operation that does not modify any data. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_STORE_UPDATE` | Store update | Updates the store configuration including currency, name, and associated products. This allows you to modify your Ticket Tailor store settings such as changing the currency, updating the store name, or managing which products are available in the store. The currency can be set to various supported currencies, and products can be added or removed by providing an array of product IDs. Empty products array will remove all products from the store. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_TICKET_GROUP_DELETE` | Ticket group delete | Delete a ticket group. This action is irreversible. The ticket group will be permanently removed and any associated ticket types and bundles will be removed from the group. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_TICKET_GROUP_UPDATE` | Ticket group update | Updates an existing ticket group. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_TICKET_TYPE_DELETE` | Ticket type delete | Delete a ticket type. This action is irreversible. The ticket type will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_TICKET_TYPE_UPDATE` | Ticket type update | Updates an existing ticket type. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHER_BY_ID_GET` | Voucher by id get | Returns a voucher by its unique identifier. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHER_CODES_GET` | Voucher codes get | Returns a list of voucher codes. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHER_CODE_VOID` | Voucher code void | Voids a voucher code. This action is irreversible. This will only mark one voucher code as voided, and will not impact the other related codes. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHER_CREATE` | Voucher create | Creates a new voucher system with associated voucher codes. Vouchers are flexible promotional tools that can be used as either promotional codes (for marketing campaigns), or gift vouchers (for customer gifting), or as credit in lieu of a payment refund. Promotional vouchers have predefined codes, while gift vouchers and credit vouchers generate unique codes when issued. Vouchers can be restricted to specific event series and have configurable expiration dates and redemption rules. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHER_DELETE` | Voucher delete | Delete voucher and its associated voucher codes. This action is irreversible. The voucher and its voucher codes will be permanently removed. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHERS_GET` | Vouchers get | Returns a list of vouchers. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_VOUCHER_UPDATE` | Voucher update | Updates an exist ing voucher's name and properties. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_WAITLIST_SIGNUP_DELETE` | Waitlist signup delete | Delete event series waitlist signup. This action is irreversible. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |
| `TICKET_TAILOR_MCP_WAITLIST_SIGNUPS_GET` | Waitlist signups get | Returns a list of waitlist signups. Notes for LLMs: - The MCP tool inputSchema defines the parameters you should provide when calling the tool (e.g., event_series_id, bundle_id, name, price, etc.). - The API response structure is completely different from the inputSchema - it returns the actual resource data (e.g., id, name, description, created_at, etc.) as defined by the Ticket Tailor API. - Do not expect the response fields to match the input parameter names. The response will contain the full resource object(s) as returned by the Ticket Tailor API. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Ticket Tailor MCP server connects Claude Cowork to your Ticket Tailor account through Composio. Once connected, Cowork can use the available Ticket Tailor tools and triggers to complete tasks on your behalf.

## Complete Code

None listed.

## How to build Ticket Tailor MCP Agent with another framework

- [ChatGPT Work](https://composio.dev/toolkits/ticket_tailor_mcp/framework/chatgpt)
- [Hermes](https://composio.dev/toolkits/ticket_tailor_mcp/framework/hermes-agent)

## Related Toolkits

- [Youtube](https://composio.dev/toolkits/youtube) - YouTube is a leading video-sharing platform for uploading, streaming, and discovering content. It empowers creators and businesses to reach global audiences and monetize their work.
- [AllTrails MCP](https://composio.dev/toolkits/alltrails_mcp) - AllTrails MCP is a trail discovery service for hiking, biking, and running routes. Use it to find reviewed trails, photos, maps, difficulty info, and route details fast.
- [Amara](https://composio.dev/toolkits/amara) - Amara is a collaborative platform for creating and managing subtitles and captions for videos. It helps make content accessible and multilingual for global audiences.
- [Captions](https://composio.dev/toolkits/captions) - Captions provides the Mirage API for generating videos, speech, and styled captions. Use it to automate polished video creation, voiceovers, and captioning from one API.
- [Cats](https://composio.dev/toolkits/cats) - Cats is an API with a huge library of cat images, breed data, and cat facts. It makes finding adorable cat photos and trivia effortless for your apps and users.
- [Chatfai](https://composio.dev/toolkits/chatfai) - Chatfai is an AI platform that lets users talk to AI versions of fictional characters from books, movies, and games. It offers an engaging, interactive experience for fans to chat, roleplay, and explore creative dialogues.
- [Cincopa](https://composio.dev/toolkits/cincopa) - Cincopa is a multimedia platform for uploading, managing, and customizing videos, images, and audio. It helps you deliver engaging media experiences with robust APIs and flexible integrations.
- [Descript MCP](https://composio.dev/toolkits/descript_mcp) - Descript MCP is a media processing and project workflow service for creators and teams. It streamlines media import, automated processing, and job management.
- [Dungeon fighter online](https://composio.dev/toolkits/dungeon_fighter_online) - Dungeon Fighter Online (DFO) is an arcade-style, side-scrolling action RPG packed with dynamic combat and progression. Play solo or with friends to battle monsters, complete quests, and upgrade your characters.
- [Elevenlabs](https://composio.dev/toolkits/elevenlabs) - Elevenlabs is an advanced AI voice generation platform for lifelike, multilingual speech synthesis. Perfect for creating natural voices for videos, apps, and business content in seconds.
- [Elevenreader](https://composio.dev/toolkits/elevenreader) - Elevenreader is an AI-powered text-to-speech service by ElevenLabs that converts written content into lifelike audio. It enables fast, natural audio generation from any text.
- [Epic games](https://composio.dev/toolkits/epic_games) - Epic Games is a leading video game publisher and digital storefront, known for Fortnite and Unreal Engine. It lets gamers access, manage, and purchase games all in one place.
- [Eranol](https://composio.dev/toolkits/eranol) - Eranol is an API-driven media conversion service for video, audio, and FFmpeg workflows. It helps teams automate reliable transcoding, format conversion, and media processing at scale.
- [Fal.ai](https://composio.dev/toolkits/fal_ai) - Fal.ai is a generative media platform offering 600+ AI models for images, video, voice, and audio. Developers use Fal.ai for fast, scalable access to cutting-edge generative AI tools.
- [Giphy](https://composio.dev/toolkits/giphy) - Giphy is the largest online library for searching and sharing GIFs and stickers. Instantly add vibrant animated content to your apps, chats, and workflows.
- [Headout](https://composio.dev/toolkits/headout) - Headout is a global platform for booking travel experiences, tours, and entertainment. It helps users discover and secure activities at top destinations, all in one place.
- [Imagekit io](https://composio.dev/toolkits/imagekit_io) - ImageKit.io is a cloud-based media management platform for image and video delivery. Instantly optimize, transform, and deliver visuals globally via a lightning-fast CDN.
- [Listennotes](https://composio.dev/toolkits/listennotes) - Listennotes is a powerful podcast search engine with a massive global database. Discover, search, and curate podcasts from around the world in seconds.
- [News api](https://composio.dev/toolkits/news_api) - News api is a REST API for searching and retrieving live news articles from across the web. Instantly access headlines, coverage, and breaking stories from thousands of sources.
- [RAWG Video Games Database](https://composio.dev/toolkits/rawg_video_games_database) - RAWG Video Games Database is the largest video game discovery and info service. Instantly access comprehensive details, ratings, and release dates for thousands of games.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Ticket Tailor MCP?

With a standalone Ticket Tailor MCP server, the agents and LLMs can only access a fixed set of Ticket Tailor tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ticket Tailor and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ticket Tailor tools.

### Can I manage the permissions and scopes for Ticket Tailor while using Tool Router?

Yes, absolutely. You can configure which Ticket Tailor scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ticket Tailor data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)