PrecisionBook a discovery call
Menu

Ticket Tailor MCP for AI agents

Agents read Ticket Tailor MCP at once. Changes and sends are held for a person's approval by default.

Book a discovery callBrowse all connectors

About Ticket Tailor MCP

Ticket Tailor MCP lets agents manage events, ticket types, orders, discounts, products, check-ins, memberships, and reporting for an authorized box office.

What an agent can do in Ticket Tailor MCP

Every Ticket Tailor MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in Ticket Tailor MCP without asking first. 34 actions.

  • Check ins getReturns 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
  • Checkout form element by id getReturns 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,
  • Checkout form elements getReturns 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
  • Checkout forms getReturns 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.). - Th
  • Discount by id getReturns 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,
  • Discounts getReturns 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
  • Event by id getReturns 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, et
  • Event occurrence by id getReturns 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
  • Event occurrences getReturns 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.). -
  • Event series by id getReturns 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, pr
  • Event series getRetrieves 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, an
  • Events getRetrieves 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 indi
Show all 34
  • Hold by id getReturns 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.
  • Holds getReturns 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 res
  • Issued membership by id getReturns 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, nam
  • Issued memberships getReturns 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, pric
  • Issued ticket by id getReturns 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, p
  • Issued tickets getReturns 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.). - Th
  • Membership photo share getReturns 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 parameter
  • Membership type by id getReturns 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,
  • Membership types getReturns 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,
  • Order by id getReturns 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, et
  • Orders getRetrieves 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, pa
  • Overrides getReturns 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
  • Overview getRetrieve 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 abou
  • Ping getTests 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. Use
  • Product by id getReturns 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, e
  • Products getReturns 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
  • Store getRetrieves 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
  • Store listRetrieves 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 othe
  • Voucher by id getReturns 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, e
  • Voucher codes getReturns 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
  • Vouchers getReturns 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
  • Waitlist signups getReturns 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.). -

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 43 actions.

  • Bundle createCreates 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.).
  • Bundle deleteDelete 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.,
  • Bundle updateUpdates 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, e
  • Check in createCreates 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
  • Checkout form element updateUpdates 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, et
  • Discount createCreates 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. Y
  • Discount deleteDelete 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.
  • Discount updateUpdates 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 AP
  • Event management<usecases> 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 fo
  • Event occurrence deleteDelete 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 t
  • Event occurrence updateUpdates 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.).
  • Event series deleteDelete 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 param
Show all 43
  • Event series status changeChanges 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_i
  • Event series updateUpdates 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.). - Th
  • Hold createCreates 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
  • Hold deleteDelete 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., even
  • Hold updateUpdates 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 re
  • Issued membership createCreates 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 sho
  • Issued membership redemption createCreates 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 param
  • Issued membership updateUpdates 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.
  • Issued membership voidVoids 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 provi
  • Issued ticket createCreates 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
  • Issued ticket voidVoids 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 ticke
  • Membership type createCreates 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 MC
  • Membership type deleteDeletes 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
  • Membership type updateUpdates 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.). -
  • Order confirm paymentConfirm 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, nam
  • Order updateUpdates 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 r
  • Override createCreates 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.
  • Override updateUpdate 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 re
  • Product createCreates 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 ticke
  • Product deleteDelete 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.
  • Product updateUpdates 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
  • Store updateUpdates 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, o
  • Ticket group deleteDelete 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 t
  • Ticket group updateUpdates 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.). - Th
  • Ticket type deleteDelete 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 to
  • Ticket type updateUpdates 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
  • Voucher code voidVoids 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 p
  • Voucher createCreates 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 custom
  • Voucher deleteDelete 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 para
  • Voucher updateUpdates 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,
  • Waitlist signup deleteDelete 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, bun

Changes wait in Needs you

Changes and sends in Ticket Tailor MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

Ticket Tailor MCP questions

Can an agent change data in Ticket Tailor MCP on its own?

Not by default. Changes and sends in Ticket Tailor MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in Ticket Tailor MCP?

This connector lists 34 read actions. Reads run at once, without waiting for approval.

How does Ticket Tailor MCP connect?

It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring Ticket Tailor MCP to your agents.

Book a discovery call