From April through September 2026, the Chili Piper API and MCP server went from reading your data to creating and changing your configuration from outside the product. Here's what you can do today.
🚀 Connect Your AI Tools
The Chili Piper MCP server connects your account to the AI tools you already use, including Claude (claude.ai, Claude Desktop, and Claude Code), ChatGPT, Gemini, OpenAI Codex, and Cursor. Ask for what you want in plain language, and it reads and writes your live Chili Piper data.
For example:
- "Show me every meeting the EMEA team booked last week and which distribution sent them there."
- "Adjust distribution weights."
- "Why did this router fail to publish?"
- "Add this prospect to the Enterprise Outbound cadence."
Before you start: connecting with OAuth, which most AI tools use, requires an Admin on a paid account. For narrower access, use an API key with only the permissions you need. OAuth also works through managed MCP gateways that sign in for a whole company.
Built for agents: the server ships with ready-made prompts for common jobs, loads tools as needed to save tokens, reports progress on long tasks, and returns errors that say what to do next.
How do I connect Chili Piper via MCP?
🚀 Book Meetings Programmatically
Book a meeting without sending anyone through a Chili Piper screen. Your backend, custom frontend, voice agent, or AI assistant calls the API, picks a time, and books.
- Start from a Concierge router, a ChiliCal scheduling link, or a Handoff router, all with the same two-step pattern
- Reschedule and reassign meetings, including changing the time or host
- Suggested Times and single-use links: get ready-to-send email HTML with times included, or a one-time scheduling URL
- Render and validate forms up front, with metadata for every guest-form field
- Book over busy slots with a dedicated, separately permissioned endpoint, for teams that book through their own tools
How do I schedule Chili Piper meetings programmatically?
🚀 Build and Change Configuration
Create, edit, and delete core configuration through the API and MCP:
- Concierge, Distro, and Handoff routers, including their triggers, CRM actions, spam and enrichment steps, and Assignment Table assignees
- Scheduling links and Web Experiences, including Web Experience AI strategy and guidance
- Meeting types, with location, conferencing, Reminders, and sharing
- Distributions and routing rules, users, Smart Parameters on data fields, and workspace round-robin settings
🚀 Logs, History, and Visibility
- Logs: Distro, Chat, Concierge (including phone calls), and Web Experience logs, with filters
- History: assignment history (who got what, and when), full chat transcripts, and Meeting Prep briefs
- Booking source: the page, parameters, and UTMs a meeting was booked from
- Distribution stats: who's up next, who's on vacation or capped, and per-rep outcomes
- Audit trail: API request logs show the caller and whether a call came through MCP or the API
🚀 Admin and Integrations
- Integration health: connection status for Salesforce, HubSpot, calendars, Slack, Gong, and Outreach in one call
- User mappings: see and fix how users match their accounts in Salesforce, HubSpot, Gong, Slack, and Microsoft Teams
- Users: read and update full profiles, and send invite emails in bulk when you're ready
- Salesloft: list cadences, find prospects, and add them to a cadence
- Editable token permissions: add permissions to an existing API token without creating a new one
Heads up: adding a user through the API doesn't send an invite email by default. Pass sendInvite: true to send it.
Run into anything? Email support@chilipiper.com. Happy building! 🌶️
Comments
0 comments
Please sign in to leave a comment.