chilipiper-mcp
MCP server for ChiliPiper — route leads, generate booking links, and manage scheduling from Claude Code, Cursor, or any MCP-compatible client.
Tools
| Tool | Description |
|---|---|
route_lead | Route a lead through a Concierge router via the marketing API. Returns a booking calendar URL. |
route_concierge | Route a lead via the Concierge fire endpoint for inbound routers. |
get_booking_link | Generate a direct booking link for a queue or meeting type. |
check_config | Validate your configuration and test API connectivity. |
Setup
1. Get your credentials
- API Key: Get your ChiliPiper REST API key from your ChiliPiper admin settings
- Domain: Your ChiliPiper organization slug (the part in URLs like
calendar.chilipiper.com/YOUR-DOMAIN/...)
2. Install
git clone https://github.com/hyypeman/chilipiper-mcp.git
cd chilipiper-mcp
npm install
3. Configure in your MCP client
Claude Code
Add to your project's .mcp.json:
{
"mcpServers": {
"chilipiper": {
"command": "node",
"args": ["/path/to/chilipiper-mcp/index.js"],
"env": {
"CHILIPIPER_API_KEY": "your-api-key",
"CHILIPIPER_DOMAIN": "your-domain"
}
}
}
}
Or use the CLI:
claude mcp add chilipiper \
--command "node /path/to/chilipiper-mcp/index.js" \
--env CHILIPIPER_API_KEY=your-api-key \
--env CHILIPIPER_DOMAIN=your-domain
Cursor / Other MCP clients
Use the same stdio configuration — command: "node", args: ["/path/to/index.js"] with the environment variables above.
Environment Variables
| Variable | Required | Description |
|---|---|---|
CHILIPIPER_API_KEY | Yes | Your ChiliPiper REST API key |
CHILIPIPER_DOMAIN | Yes | Your organization's ChiliPiper domain slug |
Example Usage
Once connected, you can ask your AI assistant things like:
- "Route this lead to the inbound-demo router: john@acme.com"
- "Generate a booking link for the sales-team queue"
- "Check if my ChiliPiper config is working"
License
MIT