Chili Piper documentation

What it does

Inbound lead routing and meeting-scheduling platform - converts web-form submissions and inbound leads into booked meetings in seconds, with rep-availability and fairness-rule logic.

Access and connection

MCP support: official

Access requirements: paid - PulseMCP's listing explicitly notes the server is a "paid service (no free tier available)"; MCP/programmatic scheduling ships in the Routing & Scheduling tier and above.

Authentication: Two supported paths, both vendor-documented. Option A (vendor-recommended): a Chili Piper Edge API key, generated by an admin in Command Center and passed as "Authorization: Bearer <key>", usable by non-admins and scopable per permission (api.ping, meeting.read, concierge.read, availability.read, handoff.schedule, user.read, workspace.read, team.read, rule.read). Option B: browser OAuth login, admin role required. PulseMCP lists only OAuth; the vendor marketing page lists only the API key. Neither source is wrong, each is partial.

Research checked: 2026-08-25

These details come from the catalog research. Check the vendor sources below for current setup instructions. They do not establish that a connection or tool call was tested.