Tito MCP server
Tito in any MCP client, through Memtro: Tito does not publish this server. Memtro's Tito connector reads Tito 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
Tito event ticketing: events (upcoming, past, archived), ticket types with sales counts, registrations with who booked and their state, and tickets with attendee name, company and ticket type. Registrations sync hourly. Can also create, edit, cancel, refund and mark paid registrations, add, edit, reassign and void tickets, manage discount codes, and pause or resume sales of a ticket type.
Reads
tito_eventsTito events for the account: title, slug, dates, location, live or not, public link.tito_releasesTicket types (releases) on a Tito event: id (what tickets, registrations and discount codes take), slug, title, price, quantity on offer…tito_registrationsRegistrations (orders) on a Tito event: reference, who booked (name, email, company), state, number of tickets, when made.tito_ticketsTickets (attendees) on a Tito event: reference, attendee name, email and company, ticket type, state (complete, incomplete, unassigned), tags.tito_discount_codesDiscount codes on a Tito event: id (what the update and delete tools take), code, money-off or percent-off and by how much…
Acts, when you ask
These change something in Tito. 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.
tito_create_registrationCreates a registration (an order) on a Tito event for the named person, with one or more tickets of the ticket types given…tito_update_registrationEdits a registration on a Tito event: the booker's name, email, company, purchase order number (payment_reference) or source code.tito_cancel_registrationCancels a registration on a Tito event and voids every ticket on it, so none of them can check in.tito_refund_registrationRefunds a registration on a Tito event.tito_mark_registration_paidMarks a pay-by-invoice registration on a Tito event as paid (paid true) or back to unpaid (paid false, for a mistaken mark).tito_create_ticketAdds a single ticket of one ticket type (release id from tito_releases) to a Tito event, for the attendee named.tito_update_ticketEdits a ticket on a Tito event: the attendee's first or last name, email, company or tags (tags replace the ticket's tags).tito_reassign_ticketReassigns a ticket on a Tito event to a new attendee.tito_void_ticketVoids a ticket on a Tito event so it can no longer check in.tito_create_discount_codeCreates a discount code on a Tito event: money off per ticket (MoneyOffDiscountCode) or a percentage (PercentOffDiscountCode)…tito_update_discount_codeChanges a discount code on a Tito event (id from tito_discount_codes): its code, type, value, uses, ticket types or window.tito_delete_discount_codePermanently deletes a discount code from a Tito event (id from tito_discount_codes); anyone holding it can no longer use it.tito_set_release_on_salePuts a ticket type (release slug from tito_releases) on a Tito event on sale (on_sale true) or pauses its sale (on_sale false).
Connect it
First connect Tito on Dashboard → Connections, then add Memtro to your client once. The Tito 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 Tito 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 sold for our next event?
- › Is Sarah Chen registered for the conference?
- › Which ticket types have sold out?
- › Who from BigCo has booked?
- › Create a 20% discount code SPEAKERS for the autumn conference, limited to 10 uses.
Questions
- Is this an official Tito MCP server?
- No. It is Memtro's MCP server with Memtro's Tito connector behind it: the connector reads Tito through its API with the credentials you connect on Dashboard → Connections, and Tito 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 Tito?
- Only when you ask, and only what it has been granted: create a registration for named ticket types, emailing the registrant only when asked; edit a registration's name, email, company, purchase order or source; cancel a registration and void its tickets; refund a registration through the payment provider, or record a manual refund; mark an invoiced registration paid, or back to unpaid; add a ticket for an attendee, or edit an attendee's name, email, company or tags; reassign a ticket to a new attendee, which emails them; void a ticket so it can no longer check in; create, change or delete a discount code; put a ticket type on sale or pause its sale. 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.