Chili Piper (MCP)

Connect AI tools to Chili Piper via the Model Context Protocol (MCP) to manage users, routing rules, distributions, and meetings

🚀 Quickstart

Connect to the Chili Piper MCP server with Tenklo and call MCP tools in minutes. Chili Piper MCP uses OAuth 2.0 with dynamic client registration, so no app registration is required — just an Admin account on a paid Chili Piper plan.

Create the integration

In Tenklo (free signup), go to Integrations -> Configure New Integration -> Chili Piper (MCP).

Authorize Chili Piper

Go to Connections -> Add Test Connection -> Authorize, then log in to Chili Piper as an Admin. Later, you'll let your users do the same directly from your app.

Call a Chili Piper MCP tool

Make your first MCP request (initialize handshake). Replace the placeholders below with your API key, integration ID, and connection ID:

curl "https://api.tenklo.dev/proxy/" \
  -X POST \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
        "protocolVersion": "2024-11-05",
        "capabilities": {},
        "clientInfo": {
            "name": "nango-client",
            "version": "1.0.0"
        }
    }
}'

✅ You're connected! Check the Logs tab in Tenklo to inspect requests.

Implement Tenklo in your app

Follow our Auth implementation guide to integrate Tenklo in your app.

📚 Chili Piper (MCP) guides

Tenklo uses dynamic client registration with Chili Piper's MCP OAuth server. You do not need to register an application — just create the integration in Tenklo and authorize with an Admin account on a paid Chili Piper plan.

Chili Piper's MCP server exposes tools that can modify production data (creating users, adjusting distributions, cancelling meetings, deleting rules). Review each tool call before letting it run against a production account.

For automation or CI use cases, or to call Chili Piper's REST endpoints directly instead of through MCP, see the Chili Piper integration, which authenticates with an API key instead.

Official resources: How do I connect Chili Piper via MCP?


On this page