Vendor: chilipiper.com · entry id 10-chili-piper · source 10-scheduling-routing.md line 45
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 on 2026-08-25 and has not been re-fetched since.
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)
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.
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.
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:
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 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.
This page is the canonical home. The listing below is the same product, counted separately in the source markdown.
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 293 entries are cross listed like this. They are why the entry count is 293 and the unique product count is 277. The canonical home is declared in INDEX.md, not chosen by the parser.
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
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.