Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Ticket Tailor
Run a Ticket Tailor box office: create events, issue and void tickets, manage orders, discounts, holds.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
What the Ticket Tailor connector does
The Ticket Tailor MCP server connects an event organiser's Ticket Tailor box office to Claude, ChatGPT, Cursor and any MCP-compatible agent. It exposes 65 tools covering events, ticket types, orders, discounts, vouchers, holds and check-ins. Thirty-six of them write. It can issue and void tickets and delete live events, and issuing bills one credit per ticket.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Ticket Tailor tools (65)
- bundle_create
- bundle_delete
- bundle_update
- check_in_create
- check_ins_get
- checkout_form_element_by_id_get
- checkout_form_element_update
- checkout_form_elements_get
- checkout_forms_get
- discount_by_id_get
- discount_create
- discount_delete
- discount_update
- discounts_get
- event_by_id_get
- event_occurrence_by_id_get
- event_occurrence_create
- event_occurrence_delete
- event_occurrence_update
- event_occurrences_get
- event_series_by_id_get
- event_series_create
- event_series_delete
- event_series_get
- event_series_status_change
- event_series_update
- events_get
- hold_by_id_get
- hold_create
- hold_delete
- hold_update
- holds_get
- issued_ticket_by_id_get
- issued_ticket_create
- issued_ticket_void
- issued_tickets_get
- order_by_id_get
- order_confirm_payment
- order_update
- orders_get
- override_create
- override_update
- overrides_get
- overview_get
- ping_get
- product_by_id_get
- product_create
- product_delete
- product_update
- products_get
- store_get
- store_list
- store_update
- ticket_type_create
- ticket_type_delete
- ticket_type_update
- voucher_by_id_get
- voucher_code_void
- voucher_codes_get
- voucher_create
- voucher_delete
- voucher_update
- vouchers_get
- waitlist_signup_delete
- waitlist_signups_get
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.accessis 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-Limitand related headers, withRetry-Aftersent 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_createfails 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
readOnlyHintordestructiveHintvalues 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, soprompts/listandresources/listwere 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.
Sources
- Ticket Tailor MCP documentation, "What is MCP" (retrieved 2026-08-21; source of the MCP framing, and both the
/mcpand/sseendpoints) · retrieved 2026-08-21 - Ticket Tailor MCP documentation, "Available tools" (retrieved 2026-08-21; source of the six functional groupings, the membership tools absent from the directory, the "all Ticket Tailor API endpoints as tools" statement, and the credit-per-issued-ticket warning) · retrieved 2026-08-21
- Ticket Tailor MCP documentation, "Authentication" (retrieved 2026-08-21; source of OAuth 2.1, the Settings → API key flow, and the key-handling warning) · retrieved 2026-08-21
- Ticket Tailor MCP documentation, "Error handling" (retrieved 2026-08-21; source of the 401/403/404/409/422 meanings including the delete-with-orders conflict example) · retrieved 2026-08-21
- Ticket Tailor MCP documentation, "Troubleshooting" (retrieved 2026-08-21; source of the API-key permission guidance and the real-time data note) · retrieved 2026-08-21
- Ticket Tailor MCP documentation, "Usage examples" (retrieved 2026-08-21; source of the natural-language examples paraphrased in the use cases) · retrieved 2026-08-21
- Ticket Tailor API reference, Introduction (retrieved 2026-08-21; source of the 5,000-per-30-minutes rate limit, the 30-per-hour membership cap, the rate-limit headers, the one-box-office-per-key rule and the error table) · retrieved 2026-08-21
- Ticket Tailor API reference, Create an issued ticket (retrieved 2026-08-21; source of the credit charge, the no-inventory failure and the seated-ticket-type exclusion) · retrieved 2026-08-21
- Ticket Tailor API reference, Void an issued ticket (retrieved 2026-08-21; source of "irreversible", the no-refund statement and the void-to-hold behaviour) · retrieved 2026-08-21
- Ticket Tailor API reference, Confirm an offline payment has been paid (retrieved 2026-08-21) · retrieved 2026-08-21
- Ticket Tailor API reference sitemap, 89 endpoint pages (retrieved 2026-08-21; the basis for the no-refund, no-email and no-resend finding, and for the 12 membership and 3 ticket-group endpoint counts) · retrieved 2026-08-21
- Ticket Tailor help centre
llms.txtmachine index (retrieved 2026-08-21; source of the refund, resend and email-broadcast articles that establish these as box-office UI tasks) · retrieved 2026-08-21 - Ticket Tailor help centre, connecting to an AI agent (the URL Anthropic's directory nominates; the host served a Cloudflare interstitial to us on 2026-08-21, so nothing on this page is sourced from it — its
llms.txtindex summarises it as finding AI Assist in "Connect apps") · retrieved 2026-08-21 - Live OAuth posture check —
initializehandshake tohttps://mcp.tickettailor.ai/mcpreturned HTTP 401 with aBearer realm="OAuth"challenge (2026-08-21). No tool was called and no authentication was attempted · retrieved 2026-08-21 - Live RFC 9728 probe of all three path forms, and the authorization-server metadata at
https://mcp.tickettailor.ai/.well-known/oauth-authorization-server(2026-08-21; source of themcp.accessscope) · retrieved 2026-08-21 - Anthropic connector directory (snapshot 2026-08-16; source of the 65 tool names, the "Read and write" permissions label, the partner tier, the financial-services category, an empty prompt list, and the festival and discount-code examples quoted in the use cases) · retrieved 2026-08-16
- Ticket Tailor support — · Privacy (both listed by Anthropic's directory; both served us a Cloudflare bot challenge on 2026-08-21, so neither is cited for any claim here) · retrieved 2026-08-21
More Finance connectors
Aiera
Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.
Airwallex Developer
Search Airwallex documentation and exercise a sandbox account from an AI agent.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Ticket Tailor to work.
Connect Ticket Tailor once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.