Look up events, releases, tickets, registrations and discount codes, and edit tickets and codes. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"tito": {
"url": "https://tito.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"tito": {
"type": "http",
"url": "https://tito.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Tito Admin API token.
Optional: Default account slug.
Create a token at id.tito.io → API access → Generate New Token and copy the secret token. A token is either live or test mode and only sees tickets and registrations of that mode. The account slug is the first part of your event URL ti.to/<account>/<event>; set it so tools can omit account_slug. Your token is used only to call the Tito API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Tito Admin API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Tito connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
tito_whoami | read | Check the API token Confirm the API token works and list the account slugs it can reach, plus its lookup mode (live or test — a token only sees tickets and registrations of its own mode). Call this first to discover account_slug. Tito: GET /hello. |
tito_list_events | read | List events List an account's events: upcoming (default), past or archived. Each has its slug, title, dates, location, currency, live/test_mode flags and public URL. Tito: GET /:account/events, /events/past, /events/archived. |
tito_get_event | read | Get one event Fetch a single event by slug: title, description, dates and times, time zone, location, currency, live/test_mode, and its releases. Tito: GET /:account/:event. |
tito_list_releases | read | List releases (ticket types) List an event's releases — Tito's ticket types — with price, quantity, tickets_count sold, sold_out / off_sale / secret flags, sale window and share_url. Tito: GET /:account/:event/releases. |
tito_get_release | read | Get one release Fetch a single release (ticket type) by slug, with pricing, capacity, sales counts (full-price, discounted, free, voided), questions and activities. Tito: GET /:account/:event/releases/:release_slug. |
tito_list_tickets | read | List tickets (attendees) List an event's tickets — one per attendee — newest first, with name, email, company, reference, release, price paid and state. Filter by free text (name, email, phone, reference, company, tag), state, type, release, activity, and created/updated time. Void tickets are excluded unless states includes 'void'. Tito: GET /:account/:event/tickets. |
tito_get_ticket | read | Get one ticket Fetch a single ticket by slug (ti_...), with the attendee, registration, release, question answers, tags and amounts paid. Tito: GET /:account/:event/tickets/:ticket_slug. |
tito_list_registrations | read | List registrations (orders) List an event's registrations — Tito's orders — newest first, with buyer name/email, reference, total, state, paid/refunded flags, discount code and ticket quantities. Filter by free text (email, name, slug, reference, company, discount code), state, and created/updated time. Cancelled ones are excluded unless states includes 'cancelled'. Tito: GET /:account/:event/registrations. |
tito_get_registration | read | Get one registration Fetch a single registration (order) by slug (reg_...), with its tickets, receipts, refunds, line items, billing address and payment details. Tito: GET /:account/:event/registrations/:registration_slug. |
tito_list_discount_codes | read | List discount codes List an event's discount codes with code, type (PercentOffDiscountCode / MoneyOffDiscountCode), value, quantity and quantity_used, validity window and attached releases. Tito: GET /:account/:event/discount_codes. |
tito_get_discount_code | read | Get one discount code Fetch a single discount code by its numeric id, including how many times it has been used. Tito: GET /:account/:event/discount_codes/:discount_code_id. |
tito_list_activities | read | List activities List an event's activities — sessions, workshops or dinners beyond the ticket itself — with capacity, allocation_count, sold_out, date/times and attached releases. Tito: GET /:account/:event/activities. |
tito_list_questions | read | List questions List the custom questions an event asks attendees (e.g. dietary requirements, t-shirt size) with slug, field_type, required flag and answers_count. Use a question's slug with tito_list_answers. Tito: GET /:account/:event/questions. |
tito_list_answers | read | List answers to a question List every attendee's answer to one question, each with its ticket_id and the response text. Tito: GET /:account/:event/questions/:question_slug/answers. |
tito_list_checkin_lists | read | List check-in lists List an event's check-in lists (the door lists used at the venue) with title, slug, the releases/activities they cover and which attendee fields they show. Tito: GET /:account/:event/checkin_lists. |
tito_list_refunds | read | List refunds List the refunds recorded for an event, each with amount, created_at, whether it was manual, and the registration it belongs to. Read-only: this server never issues refunds. Tito: GET /:account/:event/refunds. |
tito_create_discount_code | write | Create a discount code Create a discount code for an event. type is PercentOffDiscountCode (value = percent) or MoneyOffDiscountCode (value = flat amount off per ticket, in the event currency). Undo by editing it (e.g. quantity or end_at) with tito_update_discount_code. Tito: POST /:account/:event/discount_codes. |
tito_update_discount_code | write | Update a discount code Change an existing discount code — its code, value, quantity, validity window or attached releases. Only the fields you pass are sent. To retire a code without deleting it, set end_at to now. Tito: PATCH /:account/:event/discount_codes/:discount_code_id. |
tito_create_ticket | write | Issue a ticket manually Issue a ticket for a release without a checkout — e.g. a speaker, sponsor or comp ticket. Tito creates a manual registration for it. This creates a real ticket that counts against the release's capacity (undo only by voiding it in the Tito dashboard). Tito: POST /:account/:event/tickets. |
tito_update_ticket | write | Update a ticket's attendee details Correct a ticket's attendee details — name, email, company, phone, tags or metadata. Only the fields you pass are sent, and no email is sent to anyone (unlike a reassignment, which this server does not do). Tito: PATCH /:account/:event/tickets/:ticket_slug. |
tito_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
tito_request_feature | Request a missing feature Tell usefulapi that the user needs something the Tito tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
tito_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Tito (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $19/month or $190/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
tito_cancel_subscription | Cancel the Pro subscription Cancel the caller's Tito Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run tito_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Tito server only. Subscribe with tito_upgrade (it returns a Stripe Checkout link). Cancel any time with tito_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running tito_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Tito. The server calls the Tito API with your own Tito access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Tito Admin API token. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Tito Admin API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Tito API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Tito.
Yes, if you approve it. 4 of the 20 Tito tools can create or change data. The other 16 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Tito server only. Cancel any time: Pro then runs to the end of the paid period. Run tito_usage_status to see how many calls you used.
Ask the AI to run tito_upgrade: it returns a Stripe Checkout link. To cancel, run tito_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with tito_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.