chilipiper-mcp
by hyypeman
README.md
# chilipiper-mcp
MCP server for [ChiliPiper](https://www.chilipiper.com/) — 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
```bash
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`:
```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:
```bash
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
TDQS
B3.4/5.0
Scored across 4 tools
Disambiguation3/5
Most tools are distinct, but route_concierge and route_lead overlap significantly in purpose and output, potentially causing confusion for an agent.
Naming Consistency5/5
All tools use a consistent verb_noun pattern in snake_case (check_config, get_booking_link, route_concierge, route_lead).
Tool Count5/5
With 4 tools, the set is appropriately scoped for a lead routing and booking service, covering core actions without being unwieldy.
Completeness3/5
The set covers configuration, booking link generation, and lead routing, but lacks tools for managing queues, updating settings, or handling lifecycle operations.
Maintenance
ActivityInactive
ResponsivenessNo issues