# Chili Piper MCP server

> Manage Chili Piper scheduling links, meetings, routing rules and teams from your assistant. Admin only and experimental.

- Listing: https://mcp.tc/i/chili-piper
- Connect: use the server's own URL `https://fire.chilipiper.com/api/fire-edge/v1/org/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [CRM, Sales & Support](https://mcp.tc/c/crm-sales)
- Vendor: Chili Piper
- Homepage: <https://fire.chilipiper.com/>

## About

Connects to Chili Piper, the meeting scheduling and lead routing platform. According to its registry listing, it lets you manage scheduling links, meetings, routing rules and teams.

It runs as a hosted streamable HTTP endpoint at fire.chilipiper.com. Users sign in with OAuth. The listing says access is for admins only and the server is experimental, so behavior may change.

## What it can do

- Manage scheduling links
- Manage meetings
- Manage routing rules
- Manage teams

## Example prompts

- "List the scheduling links in our Chili Piper workspace"
- "Show the current routing rules for inbound leads"
- "Which teams are set up in Chili Piper?"
- "Find upcoming meetings booked through Chili Piper"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http chili-piper https://fire.chilipiper.com/api/fire-edge/v1/org/mcp
```

2. Start Claude Code, type `/mcp`, pick **chili-piper** and choose **Authenticate**. A browser window opens for the Chili Piper sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Chili Piper** and paste this URL:

```url
https://fire.chilipiper.com/api/fire-edge/v1/org/mcp
```

3. Click **Add**, then **Connect**, and sign in when Chili Piper asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Chili%20Piper&connectorUrl=https%3A%2F%2Ffire.chilipiper.com%2Fapi%2Ffire-edge%2Fv1%2Forg%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://fire.chilipiper.com/api/fire-edge/v1/org/mcp` and click **Add**.

3. Click **Connect** and sign in when Chili Piper asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://fire.chilipiper.com/api/fire-edge/v1/org/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Chili Piper to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=chili-piper&config=eyJ1cmwiOiJodHRwczovL2ZpcmUuY2hpbGlwaXBlci5jb20vYXBpL2ZpcmUtZWRnZS92MS9vcmcvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "chili-piper": {
      "url": "https://fire.chilipiper.com/api/fire-edge/v1/org/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=chili-piper&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Ffire.chilipiper.com%2Fapi%2Ffire-edge%2Fv1%2Forg%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"chili-piper","type":"http","url":"https://fire.chilipiper.com/api/fire-edge/v1/org/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "chili-piper": {
      "type": "http",
      "url": "https://fire.chilipiper.com/api/fire-edge/v1/org/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "chili-piper": {
      "serverUrl": "https://fire.chilipiper.com/api/fire-edge/v1/org/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add chili-piper --url https://fire.chilipiper.com/api/fire-edge/v1/org/mcp
codex mcp login chili-piper
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.chili-piper]
url = "https://fire.chilipiper.com/api/fire-edge/v1/org/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http chili-piper https://fire.chilipiper.com/api/fire-edge/v1/org/mcp
```

Then, inside Gemini CLI, run `/mcp auth chili-piper` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "chili-piper": {
      "type": "http",
      "url": "https://fire.chilipiper.com/api/fire-edge/v1/org/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://fire.chilipiper.com/api/fire-edge/v1/org/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-06
- Updated: 2026-10-06

---
Source: https://mcp.tc/i/chili-piper (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
