Chili Piper MCP server
Chili Piper in any MCP client, through Memtro: Chili Piper does not publish this server. Memtro's Chili Piper connector reads Chili Piper 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
Chili Piper: meetings booked in a window of up to a week with status, guests and the assigned rep, the routers that route leads and handoffs, users, workspaces and personal meeting types. Can book a meeting for a host, cancel a meeting, mark it showed or no-show, set a rep Available or Away for live routing, turn a Distro router on or off, and invite a user, each only when asked.
Reads
chilipiper_meetingsChili Piper meetings in a window of at most 7 days (scheduled time, as far as Chili Piper documents it): meeting id, status (Active, Canceled…chilipiper_routersChili Piper routers: Distro (routes CRM records to reps; with activation status and trigger), Handoff (SDR-to-AE handoffs…chilipiper_usersChili Piper users, in one workspace or the whole org: id, name, email, timezone and whether a super admin.chilipiper_workspacesChili Piper workspaces: id and name.chilipiper_personal_meeting_typesChili Piper personal meeting types (each user's own booking pages): id, name, slug, duration, whether active, and the personal workspace it lives in.
Acts, when you ask
These change something in Chili Piper. 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.
chilipiper_create_meetingBook a Chili Piper meeting for one host on one of their personal meeting types, at a free start time, with a guest.chilipiper_cancel_meetingCancel a Chili Piper meeting.chilipiper_mark_meeting_no_showMark a Chili Piper meeting as a no-show (the guest did not attend).chilipiper_mark_meeting_showedMark a Chili Piper meeting as attended.chilipiper_set_user_availabilitySet a Chili Piper user Available or Away for Concierge Live and Handoff Live.chilipiper_activate_distro_routerTurn a Chili Piper Distro router on so it starts assigning CRM records to people.chilipiper_deactivate_distro_routerTurn a Chili Piper Distro router off so it stops assigning CRM records.chilipiper_invite_userCreate a Chili Piper user account for a person, with a role, licences and workspaces.
Connect it
First connect Chili Piper on Dashboard → Connections, then add Memtro to your client once. The Chili Piper 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 Chili Piper 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 Chili Piper meetings were no-shows this week?
- › Which meetings is Dan Fletcher assigned next week?
- › Which Distro routers are active?
- › Has jane@bigco.com booked a meeting this week?
- › Mark my 2pm with Globex as a no-show
Questions
- Is this an official Chili Piper MCP server?
- No. It is Memtro's MCP server with Memtro's Chili Piper connector behind it: the connector reads Chili Piper through its API with the credentials you connect on Dashboard → Connections, and Chili Piper 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 Chili Piper?
- Only when you ask, and only what it has been granted: book a meeting for a host on their personal meeting type (sends calendar invites to the guest); cancel a meeting (permanent, may email attendees); mark a meeting as a no-show (may update the CRM and run workflows); mark a meeting as attended (may update the CRM and run workflows); set a user Available or Away for live routing; turn a Distro router on so it routes records; turn a Distro router off so it stops routing records; invite a user to Chili Piper (emails them only if asked). 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.