# Chili Piper: MCP server status, API access gate and what it does > Inbound lead-routing and instant meeting-booking platform ("Concierge") that qualifies web-form leads and... Official MCP, Paid, self-serve. Checked 2026-08-25. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Scheduling & Routing](../categories/scheduling-routing.md) / Chili Piper # Chili Piper [Official MCP](../mcp/official.md) [Paid, self-serve](../gates/paid.md) [Scheduling & Routing](../categories/scheduling-routing.md) RESEARCHED Checked 2026-08-25 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [chilipiper.com](https://chilipiper.com) · entry id 10-chili-piper · source 10-scheduling-routing.md line 45 **What it does** Inbound lead-routing and instant meeting-booking platform ("Concierge") that qualifies web-form leads and books them directly onto the right rep's calendar in real time. **AI features, separated from automation with an AI label on it** Vendor markets several AI-branded features - Chat AI (24/7 visitor qualification and booking), Chili Assist ("build routing rules in plain English"), AI agents for ICP scoring/intent detection, a spam checker, and pre-call meeting prep - but underlying model mechanics are not disclosed publicly; treat as vendor-stated. The core routing engine (queues, round robin, territory rules) is conventional rules-based distribution logic wrapped in a natural-language config layer. **RevOps role** Inbound lead-routing plus meeting-booking layer sitting between web forms/CRM and reps' calendars; also positions itself as infrastructure other AI SDR/voice agents call to book meetings end-to-end. **MCP server** - **Status bucket**: Official MCP - **Auth**: 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 ", 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. - **Parsed URLs**: 4 found in the mcp_url field - **Endpoint probe**: docs page, not an endpoint - **Docs URL**: [https://www.chilipiper.com/products/mcp](https://www.chilipiper.com/products/mcp) - **Probed**: 2026-09-04, HTTP 200 The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-25. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second. mcp_status, verbatim from the file: official mcp_url, verbatim from the file: https://www.chilipiper.com/products/mcp (endpoint: https://fire.chilipiper.com/api/fire-edge/v1/org/mcp, HTTP transport; setup README: https://github.com/Chili-Piper/mcp-assets/blob/main/mcp-servers/chili-piper/README.md; registry listing: https://www.pulsemcp.com/servers/chili-piper, server id com.chilipiper/mcp) - [https://www.chilipiper.com/products/mcp](https://www.chilipiper.com/products/mcp) - [https://fire.chilipiper.com/api/fire-edge/v1/org/mcp](https://fire.chilipiper.com/api/fire-edge/v1/org/mcp) - [https://github.com/Chili-Piper/mcp-assets/blob/main/mcp-servers/chili-piper/README.md](https://github.com/Chili-Piper/mcp-assets/blob/main/mcp-servers/chili-piper/README.md) - [https://www.pulsemcp.com/servers/chili-piper](https://www.pulsemcp.com/servers/chili-piper) **What this server exposes** - **Tools named**: 2 - **Strongest evidence**: in a README table - **Harvested**: 2026-09-27 - **Repo read**: Chili-Piper/mcp-assets - **Whose repo**: first-party - **Catalogue shape**: a fixed catalogue the vendor publishes A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything. - **Folder** What it is evidence: in a README table · calling it reads - **Skill** What it does evidence: in a README table · calling it reads 141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the [tools index](../tools-index.md). **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Paid, self-serve - **Can a solo operator reach it**: Yes, by paying, no sales call api_gate, verbatim from the file: paid - MCP/programmatic scheduling ships inside the "Routing & Scheduling" tier and above, starting around $1,250/mo ($15K/yr, 15 seats included per one source). PulseMCP states plainly "paid service (no free tier available)". Not accessible to a solo operator without a paid contract. **API documentation** [https://help.chilipiper.com/hc/en-us/sections/4413992727699-API-References-Edge-API](https://help.chilipiper.com/hc/en-us/sections/4413992727699-API-References-Edge-API) No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health: - [https://github.com/Chili-Piper/mcp-assets](https://github.com/Chili-Piper/mcp-assets) - [https://github.com/Chili-Piper/mcp-assets/blob/main/mcp-servers/chili-piper/README.md](https://github.com/Chili-Piper/mcp-assets/blob/main/mcp-servers/chili-piper/README.md) - [https://github.com/hyypeman/chilipiper-mcp](https://github.com/hyypeman/chilipiper-mcp) **On GitHub** [github.com/Chili-Piper](https://github.com/Chili-Piper) tied to the vendor by rule 1, account website https://www.chilipiper.com/ has the vendor's domain, confidence strong - **Public repositories**: 7, forks excluded, as read on 2026-09-08 - **Mention MCP**: 1 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-09-08 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [mcp-assets](https://github.com/Chili-Piper/mcp-assets) | MCP server | Official Chili Piper Skills and ChatGPT GPTs for the Chili Piper MCP - meeting diagnostics, routing audits, no-show... | 7 | 2026-09-08 | v1.0.0 | | [terraform-provider-jitsu](https://github.com/Chili-Piper/terraform-provider-jitsu) | infrastructure | terraform provider for Jitsu | 0 | 2026-09-08 | v0.0.7 | | [Integration](https://github.com/Chili-Piper/Integration) | plugin or integration | CP Integrations repository | 0 | 2026-03-30 | | | [trivy-report-issue-action](https://github.com/Chili-Piper/trivy-report-issue-action) | infrastructure | Creates GitHub Issues from Trivy scan results. | 2 | 2025-02-20 | v1.2 | | [repository-notifier](https://github.com/Chili-Piper/repository-notifier) | other | Repository Notifier Service | 0 | 2025-01-29 | v0.2 | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **Jobs it can do** - [Book a meeting](../jobs/book-a-meeting.md) - [Read calendar availability](../jobs/read-calendar-availability.md) - [Answer an inbound chat or call](../jobs/answer-inbound-chat.md) - [Route an inbound lead](../jobs/route-inbound-lead.md) - [Score and prioritize leads](../jobs/score-and-prioritize-leads.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Also listed in another category** This page is the canonical home. The listing below is the same product, counted separately in the source markdown. - **Listed as**: Chili Piper - **Category**: [Inbound & PLG Chat](../categories/inbound-plg-chat.md) - **MCP status there**: Official MCP - **Gate there**: Paid, self-serve - **Source**: 14-inbound-plg-chat.md line 198 - **Canonical page**: [Chili Piper](../tools/chili-piper.md) What that listing says 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. 16 of the 1252 entries are cross listed like this. They are why the entry count is 1252 and the unique product count is 1236. The canonical home is declared in INDEX.md, not chosen by the parser. **Sources** - [https://www.chilipiper.com/products/mcp](https://www.chilipiper.com/products/mcp) - [https://www.chilipiper.com/pricing](https://www.chilipiper.com/pricing) - [https://github.com/Chili-Piper/mcp-assets](https://github.com/Chili-Piper/mcp-assets) - [https://www.pulsemcp.com/servers/chili-piper](https://www.pulsemcp.com/servers/chili-piper) - [https://github.com/hyypeman/chilipiper-mcp](https://github.com/hyypeman/chilipiper-mcp) - [https://apitracker.io/a/chili-piper](https://apitracker.io/a/chili-piper) 6 source URLs. Raw sources field, verbatim: https://www.chilipiper.com/products/mcp, https://www.chilipiper.com/pricing, https://github.com/Chili-Piper/mcp-assets, https://www.pulsemcp.com/servers/chili-piper, https://github.com/hyypeman/chilipiper-mcp, https://apitracker.io/a/chili-piper **Notes, verbatim from the file** DEFECT FIXED 2026-08-25. This entry and the Chili Piper entry in 14-inbound-plg-chat.md previously carried conflicting mcp_url and mcp_auth values (this file said the product page plus API key; file 14 said the PulseMCP listing plus OAuth). Neither was wrong. The vendor's own setup README documents BOTH auth paths, and each source had surfaced only one of them. Both entries now carry identical, reconciled mcp/auth/gate fields, and the real server endpoint (fire.chilipiper.com/api/fire-edge/v1/org/mcp) is recorded for the first time in either. Note the split hosts: the REST Edge API base is edge.chilipiper.com while the MCP lives on fire.chilipiper.com. The github.com/Chili-Piper/mcp-assets repo is a Claude Skills / GPT Actions asset bundle, not the server itself. A separate community MCP server also exists (github.com/hyypeman/chilipiper-mcp, MIT license, authenticates via CHILIPIPER_API_KEY plus a domain-slug env var) as a lighter-weight alternative. Third-party MCP wrappers also exist via Zapier (zapier.com/mcp/chili-piper) and viasocket.com; do not confuse any of these with Chili Piper's own official server. **Provenance** - **Entry id**: 10-chili-piper - **Source file**: 10-scheduling-routing.md - **Source line**: 45 - **Tier**: RESEARCHED - **last_checked**: 2026-08-25 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).