Is this an official Ticket Tailor MCP server?

No. It is Memtro's MCP server with Memtro's Ticket Tailor connector behind it: the connector reads Ticket Tailor through its API with the credentials you connect on Dashboard → Connections, and Ticket Tailor publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Ticket Tailor?

Only when you ask, and only what it has been granted: issue a ticket for an event to a named attendee, spending one credit, emailing them only if asked; void an issued ticket (permanent), optionally back to a hold. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Content and web

Ticket Tailor MCP server

Ticket Tailor in any MCP client, through Memtro: Ticket Tailor does not publish this server. Memtro's Ticket Tailor connector reads Ticket Tailor through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Ticket Tailor box office: events and event series with dates, tickets issued and revenue, orders with totals and status, and issued tickets with check-in state; when asked and granted, can issue a ticket to a named attendee (one credit each) or void an issued ticket. Buyer contact details are never read out.

Reads

tickettailor_list_eventsEvents (single occurrences) in the box office, with start and end, venue, tickets available and issued, and revenue.
tickettailor_list_event_seriesEvent series (the event a buyer sees, which may have many dates): status, venue, next date, number of occurrences, tickets issued and revenue.
tickettailor_list_ordersOrders in the box office, in Ticket Tailor's default order: event, status, number of tickets, subtotal, tax, total and amount paid in major units…
tickettailor_list_issued_ticketsIssued tickets: ticket type, status, order, event and whether checked in.

Acts, when you ask

These change something in Ticket Tailor. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

tickettailor_issue_ticketIssue a ticket for an event occurrence to a named attendee, from a ticket type's allocation (event_id and ticket_type_id) or from a hold (hold_id).
tickettailor_void_ticketVoid an issued ticket so it is no longer valid.

Connect it

First connect Ticket Tailor on Dashboard → Connections, then add Memtro to your client once. The Ticket Tailor tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Ticket Tailor connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How many tickets have we sold for the Acme summer meetup?
› What revenue has the Northwind workshop series taken so far?
› How many people have checked in at tonight's event?
› Which orders for the Brightwave Ltd launch were refunded?
› Issue a speaker ticket for the summer meetup to Priya Nair

Questions

Is this an official Ticket Tailor MCP server?: No. It is Memtro's MCP server with Memtro's Ticket Tailor connector behind it: the connector reads Ticket Tailor through its API with the credentials you connect on Dashboard → Connections, and Ticket Tailor publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Ticket Tailor?: Only when you ask, and only what it has been granted: issue a ticket for an event to a named attendee, spending one credit, emailing them only if asked; void an issued ticket (permanent), optionally back to a hold. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.