Ticket Tailor

Name: Ticket Tailor MCP Server
Availability: InStock
Author: Ticket Tailor

Finance65 tools

Run a Ticket Tailor box office from an AI assistant — create events, issue and void tickets, manage orders, discounts and holds. 65 tools, 36 of which write. Issuing a ticket costs one credit even when the ticket is free.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 21 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Ticket Tailor via MCP

https://mcp.tickettailor.ai/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Ticket Tailor Tools & Capabilities (65)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

No refunds, no email, no ticket transfer. None of the three exists as a tool. Ticket Tailor handles refunding, cancelling, resending a ticket and emailing buyers from the box office interface, and the API reference we checked on 2026-08-21 has no endpoint for any of them. An agent asked to "refund this customer" cannot, and the closest thing it can reach — issued_ticket_void — takes the ticket away while leaving the charge in place.
"No send tool" is not the same as "no mail is sent". Ticket Tailor's event confirmation email is what delivers tickets to attendees, and it is configured in box-office settings rather than invoked per request. Neither the create-issued-ticket reference nor the MCP documentation states whether an API-issued ticket triggers it. We could not establish this either way, and it is the question to settle before letting an agent issue tickets — the failure mode is mail reaching a real attendee as a side effect of a tool that never mentions mail.
Issuing tickets costs credits. One credit per issued ticket, free tickets included, stated by Ticket Tailor in two places. Budget before letting an agent issue in bulk.
The consent screen has one switch. mcp.access is the only scope advertised, so read-only connection is not expressible at the OAuth layer. Ticket Tailor's API keys carry their own permission settings and its troubleshooting page tells users to confirm the key has the required permissions — that is where narrowing has to happen, not at the consent screen.
One box office per key. API keys are associated to the box office that issued them and can access only that box office's data. Organisers running several will need several connections.
Rate limits. 5,000 requests per 30 minutes, reported through X-Rate-Limit-Limit and related headers, with Retry-After sent on exhaustion. Issuing memberships is capped far lower at 30 requests per hour.
Some writes are refused by state, not permission. Ticket Tailor documents 409 Conflict for resource state conflicts, giving deleting an event that already has orders as the example, and 422 for business-logic constraints such as event dates and ticket quantities.
Seated tickets are out of scope for issuing. issued_ticket_create fails on ticket types that use a seating chart, and fails rather than overselling when inventory is exhausted.
Attendee data is personal data. Orders, issued tickets, check-ins and waitlist signups carry named buyers with email addresses, and checkout form elements can carry whatever custom questions an organiser asks. Connecting the box office puts that category of record in front of the model. This page describes the categories only and reproduces no attendee record.
We could not read tool schemas or safety annotations. The endpoint answered our 2026-08-21 handshake with HTTP 401, so no parameter types and no readOnlyHint or destructiveHint values were available. Tool names come from Anthropic's directory; behaviour comes from Ticket Tailor's documentation.
No prompts or resources were observable. The 401 stops at initialize, so prompts/list and resources/list were unreachable. This is a known unknown, not an assertion that the server serves none.

Frequently asked questions

Can the Ticket Tailor MCP server refund an order?

No. There is no refund tool. We checked all 89 pages of Ticket Tailor's REST API reference on 2026-08-21 and found no refund, cancel, email or resend endpoint anywhere, and the connector exposes API endpoints as tools. Ticket Tailor documents refunding as a box-office task done from the Orders page. The connector can void a ticket, which Ticket Tailor states does not issue a refund.

What does it cost to issue a ticket through the Ticket Tailor MCP server?

One credit per issued ticket, even when the ticket is free. Ticket Tailor prints that warning twice — on its MCP available-tools page and again on the create-issued-ticket API reference. This is the one tool on the server that spends money by running, so an agent looping over a guest list bills per row. Nothing in the protocol caps the loop.

Can the Ticket Tailor connector email your ticket holders?

No tool sends mail. Ticket Tailor runs confirmation emails, broadcasts and renewal reminders from box-office settings, and none of that surface appears in the API reference or the connector's 65 tools. One caveat: the event confirmation email is what delivers tickets to attendees, and the docs do not say whether an API-issued ticket triggers it. Settle that before issuing in bulk.

Is voiding a ticket reversible in Ticket Tailor?

No. Ticket Tailor's API reference states plainly that voiding an issued ticket is irreversible. It marks the ticket invalid without cancelling the order or issuing a refund, so the buyer keeps the charge and loses the ticket. Voiding to a hold is the one variant that preserves the allocation, converting the ticket into a hold rather than returning it to sale.

How much can you decline on the Ticket Tailor consent screen?

Nothing. Ticket Tailor's authorization-server metadata advertises exactly one scope, mcp.access, so the grant is all-or-nothing across all 65 tools. Approving read access to sales reports is the same click as approving ticket voiding and event deletion. Ticket Tailor's own API keys carry permission settings, so the narrowing has to happen there instead.

Does the Ticket Tailor MCP server use an API key or OAuth?

Both, layered. Ticket Tailor documents OAuth 2.1 as the transport, but the credential you paste into the OAuth prompt is a Ticket Tailor API key generated under Settings and API. We confirmed the OAuth challenge live on 2026-08-21. An API key is bound to one box office, so a connected agent reaches that box office and no other.

Why does the Ticket Tailor connector list 65 tools when the docs describe more?

The directory snapshot predates part of the surface. Anthropic's 2026-08-16 record lists 65 tools with no membership tools, while Ticket Tailor's MCP documentation describes membership types, issued memberships and redemptions, and its API reference carries 12 membership and 3 ticket-group endpoints. The vendor says the server exposes all API endpoints, so the real surface is likely larger than 65.