PopMCP
humanitix_attendee_One page of an event's attendees, for a door list or a headcount: name, ticket type, seat and whether they are checked in.
Humanitix MCP server for your AI
See how an event is selling, find anyone by name, email or order code, follow check-in as the doors open, and check a ticket in or out from chat, on the Humanitix account you already use.
PopMCPHumanitix
How are tickets selling for the Summer Gala, by ticket type, and how much have we made so far?
Supported Humanitix tools
Every operation in the Humanitix Public API, plus tools for what it leaves to you: finding an event or a person, adding up sales, and setting check-ins against tickets sold. Humanitix's API reads events, orders, tickets and tags, and its only changes are checking tickets in and out.
18 tools in the full catalog: 16 read and 2 write. 16 load by default, and the rest are found with tool search.
humanitix_check_Mark one ticket as checked in at the door, the same as scanning it.
humanitix_check_Undo a check-in, or record someone leaving: marks one checked-in ticket as checked out.
humanitix_event_How check-in is going for one date of an event: checked in, valid tickets, not checked in, percent, and checked in per ticket type.
humanitix_find_Find a person in one event by name, email address, phone number, the short order code a buyer sees (such as 7QVD6HEL), or a ticket or order id.
humanitix_get_One ticket in full: attendee, price breakdown, seat, checkout answers and check-in history.
humanitix_list_List an event's tickets, one per attendee, with name, ticket type, price, status, seat and whether it is checked in.
humanitix_find_Find an event on this account by words from its name, venue, city or link, and get its eventId and the eventDateId of each date.
humanitix_get_How many tickets are checked in for one date of an event, in total and per ticket type.
humanitix_get_One event in full: dates (each with its eventDateId), ticket types and prices, capacity, venue, checkout questions and accessibility details.
humanitix_list_List the events on this Humanitix account, newest first as Humanitix returns them.
humanitix_event_How an event is selling: order counts by financial status, money totals per currency (gross, net, refunds, discounts, taxes, fees, donations), and tickets sold, cancelled and checked in per ticket type.
humanitix_get_One order in full, including the buyer's contact details and checkout answers.
humanitix_list_List an event's completed orders, with the buyer's name and email, money totals and financial status.
humanitix_get_One tag by tagId, from humanitix_list_tags or the tagIds on an event.
humanitix_list_List the tags on this account, used to group events.
humanitix_list_List individual event dates from every host on Humanitix, one row per date, with whether each ticket type is on sale (publicOfferStatus).
humanitix_list_List public events from every host on Humanitix, not just this account.
Connect Humanitix to Claude, ChatGPT and Claude Code
Credentials off one Humanitix screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.
In Humanitix open Account, then Advanced, then Public API key, copy the key, generating one if there is none yet, and paste it into PopMCP. No app or approval is needed. One key belongs to one host account, so there is nothing else to choose.
API key
••••••••••••3f7aConnectionVerified
Checking a ticket in or out is a write and waits until an owner or admin allows write actions; new connections start read-only. Humanitix keys have no permission settings of their own, so read-only in PopMCP is what keeps a key from changing anything. Orders and tickets hold personal data, so lists leave out phone numbers and checkout answers unless one record is asked for.
Reach Humanitix
Reach other connectors
Teammates on read-only
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Humanitix credential never leaves the server.
app.popmcp.com/mcp
Claude wants to connectApproveAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
How are tickets selling for the Summer Gala, by ticket type, and how much have we made so far?
humanitix_find_eventok
Then just ask for the work
“How are tickets selling for the Summer Gala, by ticket type, and how much have we made so far?”
- find_event
- event_sales_report
“Did grace@example.com buy a ticket to the Summer Gala, and has she arrived yet?”
- find_event
- find_attendee
“How many people have checked in tonight, and how many are we still waiting for?”
- event_check_in_report
“Find order 7QVD6HEL and check in the tickets on it”
- find_attendee
- check_in_ticket
“Give me a door list for Saturday's session with everyone's dietary answers”
- get_event
- attendee_list
“Which of my upcoming events have orders since Monday?”
- list_events
- list_orders
Use Humanitix from the assistant you already open
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Claude DesktopCustom connector
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
Claude WebCustom connector
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
ChatGPTCustom connector
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
CodexDesktop & CLI
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
OpenCodeCoding agent
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
ZCodeDesktop app
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
Explore other MCP servers
Every one of them runs on the same hosted endpoint, with the same controls.
FAQ
Humanitix MCP server questions
What teams ask before putting Humanitix behind an AI client.
What does PopMCP need to connect Humanitix?
One API key. In Humanitix open Account, then Advanced, then Public API key, and copy the key shown there, or generate one if there is none yet. Paste it into PopMCP, which checks it against Humanitix and stores it encrypted. The key never reaches your AI client. Generating a new key stops the old one working, so update anything else that uses it.
Can the AI create or change events, orders or tickets?
No. Humanitix's Public API reads events, orders, tickets and tags, and the only changes it allows are checking a ticket in and checking it out. Those two wait until an owner or admin allows write actions in PopMCP. Creating events or refunding orders stays in the Humanitix console.
What happens to attendee and buyer details?
They go to the AI client you connect when it asks, so only connect one you trust with them. To keep answers small, lists carry names, ticket details and the buyer's email, and leave out phone numbers, tax ids, order notes and checkout answers. Those appear when the AI opens one order or ticket, or asks for answers in an attendee list.
Can it find someone by the order code on their ticket?
Yes. The short code a buyer sees, such as 7QVD6HEL, is different from the id the API uses, and the API has no search. The find_attendee tool reads the event's tickets and orders and matches a name, email address, phone number or order code. On a very large event it says if it could not read them all, and narrowing to one date helps.
My events run in more than one country. Does that work?
Yes. Humanitix keeps data per market, and calls use the market of your account unless told otherwise. For an event in another market the AI passes that market, such as NZ, US, GB, or DE for the EU. Check-in counts are the one call Humanitix does not offer this on.
Which Humanitix changes can start a workflow?
Humanitix's API has no webhooks, so PopMCP watches for changes instead: events added or changed, new or changed orders and tickets, and check-ins passing a number you choose. Nothing needs setting up in Humanitix, though a change is noticed at the next check rather than the moment it happens.
Do I have to run or host the Humanitix MCP server myself?
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Which AI clients can use this MCP server?
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
How do I connect Humanitix to Claude Code?
Connect Humanitix in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Humanitix on the consent screen. The Humanitix tools are then available in that session, and no Humanitix credential is stored on your machine.
Why do only 16 of the 18 tools load by default?
Loading 18 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 16-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.
What is the difference between a tool and a trigger?
A tool is something your AI calls, and there are 18 here. A trigger is something PopMCP watches for you: 6 Humanitix events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Humanitix.
Connect Humanitix to your AI in minutes
Launch a hosted MCP endpoint for Humanitix, keep tool access under control, and start testing real workflow prompts right away.