Is this an official Humanitix MCP server?

No. It is Memtro's MCP server with Memtro's Humanitix connector behind it: the connector reads Humanitix through its API with the credentials you connect on Dashboard → Connections, and Humanitix 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 Humanitix?

Only when you ask, and only what it has been granted: check an attendee's ticket in to an event; undo an attendee's check-in (check the ticket out). 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 · Work management

Humanitix MCP server

Humanitix in any MCP client, through Memtro: Humanitix does not publish this server. Memtro's Humanitix connector reads Humanitix 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

Humanitix events: events with dates, venue, capacity and ticket types; an event's orders (buyer name, status, total); its attendees (name and ticket type); check-in counts per event date; and checking an attendee's ticket in or out.

Reads

humanitix_list_eventsEvents on the Humanitix account, with start and end, venue, capacity, ticket types and prices, and whether published.
humanitix_get_eventOne Humanitix event in full: every date it runs on (with the date ids that orders, attendees and check-in counts filter by), ticket types and prices…
humanitix_list_ordersOrders for one Humanitix event: buyer name and organisation, order and financial status, total and refunds, sales channel and when completed…
humanitix_list_attendeesAttendees (tickets) for one Humanitix event: each ticket holder's name and ticket type, with counts per ticket type.
humanitix_check_in_countHow many people have checked in to one date of a Humanitix event, in total and per ticket type.

Acts, when you ask

These change something in Humanitix. 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.

humanitix_check_in_ticketChecks one attendee's ticket in to a Humanitix event, as scanning it at the door would, and returns any scanning messages the event shows.
humanitix_check_out_ticketChecks one attendee's ticket out of a Humanitix event, undoing a check-in (a mistaken scan, or someone leaving), and returns any scanning messages.

Connect it

First connect Humanitix on Dashboard → Connections, then add Memtro to your client once. The Humanitix 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 Humanitix 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

› What events do we have coming up?
› How many tickets have we sold for the gala?
› Who is coming to Thursday's workshop?
› How many people have checked in to tonight's launch so far?
› Check in Priya Sharma for tonight's launch

Questions

Is this an official Humanitix MCP server?: No. It is Memtro's MCP server with Memtro's Humanitix connector behind it: the connector reads Humanitix through its API with the credentials you connect on Dashboard → Connections, and Humanitix 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 Humanitix?: Only when you ask, and only what it has been granted: check an attendee's ticket in to an event; undo an attendee's check-in (check the ticket out). 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.