Chili Piper

com.chilipiperPublished by chilipiper.comOfficial publisherv1.0.0Updated Oct 24, 2026

Manage Chili Piper scheduling links, meetings, routing rules, and teams. Admin only. Experimental.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Chili Piper's remote MCP server lets an assistant manage scheduling links, meetings, routing rules and teams in a Chili Piper account.

What you can do
Manage scheduling links and meetings in Chili Piper, including creating and adjusting them through the assistant. Work with routing rules that decide how incoming leads or meetings are assigned. Manage teams in the account. The server is described as admin only and experimental, and no individual tools are listed, so exact capabilities are not documented.
When to use it
Use it when an assistant should help administer a Chili Piper account: keeping scheduling links and meetings in order, adjusting routing rules, or managing teams, rather than for end-user booking.
Requirements
A remote MCP endpoint at fire.chilipiper.com, reached over streamable HTTP. OAuth authentication is required, so the user must sign in to a Chili Piper account with admin rights. No environment variables or headers are declared.
Before you install
Access is described as admin only, so the assistant can act with administrative rights on scheduling links, meetings, routing rules and teams, which may change how leads are assigned. The server is labeled experimental. OAuth grants access to the Chili Piper account; review the scopes before authorizing.

Installation

In SourceWeft

  1. Open Chili Piper in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.chilipiper%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.