Can AI agents automate Chili Piper?

Chili Piper is automatable today through the official hosted MCP at https://fire.chilipiper.com/api/fire-edge/v1/org/mcp. This record is Chili Piper routing, scheduling, handoff, meetings, users, teams, and routing rules. It is not Calendly. The MCP uses HTTP transport and, per Chili Piper engineering, exposes all public org API endpoints as tools. Documented groups include concierge routing, meeting analytics, availability, handoff, users and teams, routing rules, and distributions. API-key auth is Authorization: Bearer. Generating a key in Command Center is Admin-only; a non-admin may use a key an Admin issued. Browser OAuth on the MCP path also requires Admin, and OAuth must be enabled for the tenant. The same Edge REST API is documented as OpenAPI 3.1 at fire.chilipiper.com, version 1.372.0, with 143 paths for tenant, workspaces, users, teams, meeting types, availability, scheduling links, meetings, distributions, Distro, Concierge, Handoff, rules, CRM, chat, and webhooks. Meeting-lifecycle webhooks POST signed payloads for MeetingCreated, MeetingUpdated, and MeetingDeleted. iPaaS connector catalogs and a first-party CLI were not opened. Computer-use viability is unassessed. MCP and API both score 8. MCP is the best path for agents because it is the vendor-hosted tool surface over the same org API.

Best path today: mcp · Overall automatability: 8/10