chilipiper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHILIPIPER_DOMAIN | Yes | Your organization's ChiliPiper domain slug (the part in URLs like calendar.chilipiper.com/YOUR-DOMAIN/...) | |
| CHILIPIPER_API_KEY | Yes | Your ChiliPiper REST API key |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| route_leadC | Route a lead through a ChiliPiper Concierge router. Submits lead/form data and returns a booking calendar URL. |
| route_conciergeC | Route a lead via the ChiliPiper Concierge fire endpoint. Returns the booking calendar URL for an inbound router. |
| get_booking_linkB | Generate a direct booking link for a ChiliPiper queue or meeting type. |
| check_configA | Validate ChiliPiper MCP configuration. Shows current settings and tests API connectivity. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hyypeman/chilipiper-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server