Connect Chili Piper to Claude Code

Let Claude book meetings and route inbound leads in Chili Piper. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Chili Piper to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Chili Piper, you add a Chili Piper MCP server: a small hosted service that exposes Chili Piper's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Chili Piper account. No API keys pasted into config files.

claude mcp add --transport http chili-piper https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Chili Piper once connected?

Full read-write Chili Piper access lets Claude book a meeting into the right rep's queue, route or reassign an inbound lead, reschedule or cancel a booked call, and surface routing outcomes in a reply. The handoff that used to mean clicking through the admin console happens where you are already working.

Book a meeting for an inbound lead into the correct rep's calendar
Route or reassign a lead to a different queue or owner
Reschedule a booked meeting to a new time after you confirm
Cancel a scheduled meeting once you approve
Look up upcoming booked meetings and surface routing conflicts
Pull a rep's current availability into a draft reply

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Chili Piper access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Chili Piper API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Chili Piper changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Chili Piper connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Chili Piper connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Chili Piper account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Chili Piper's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Chili Piper?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Chili Piper account it signs in with. Revoking access is one click in Chili Piper.

More on the Chili Piper connector

Chili Piper connector for claude.ai Microsoft Bookings + Claude Code SavvyCal + Claude Code YouCanBook.me + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us