@chamade/mcp-server

MCP (Model Context Protocol) server for Chamade — a voice gateway that lets your AI agent join voice meetings and phone calls on Discord, Microsoft Teams, Google Meet, Telegram, SIP, Zoom, Nextcloud Talk, and WhatsApp.

Your agent only deals with text. Chamade handles the audio layer: joining the meeting, transcribing what people say (STT), speaking replies aloud (TTS), and relaying chat messages.

v3: hosted MCP + thin stdio shim

The Chamade MCP server is now hosted at https://mcp.chamade.io/mcp/ and speaks the Streamable HTTP transport. That's the single source of truth — every tool, every resource, every push event lives there.

• If your MCP client supports Streamable HTTP (Claude Desktop recent, Claude Code, Cursor, Windsurf, …), configure it directly against the hosted endpoint. You don't need this npm package.
• If your MCP client is stdio-only, install this package. Since v3 it's a ~160-line wrapper that spawns mcp-remote under the hood to bridge stdio to the hosted HTTP endpoint. Same tools, same push events, same latency. Zero drift because there is no parallel stdio implementation.

Earlier versions of this package (v2.x and below) shipped a full native stdio server that implemented the 13 tools locally in TypeScript against Chamade's REST API. v3 replaces that with a shim — please upgrade to avoid maintaining two surfaces that slowly diverge.

Quick start

Option A — HTTP direct (preferred)

If your client speaks Streamable HTTP, skip this package entirely:

{
  "mcpServers": {
    "chamade": {
      "type": "http",
      "url": "https://mcp.chamade.io/mcp/",
      "headers": {
        "Authorization": "Bearer chmd_..."
      }
    }
  }
}

Option B — stdio shim (this package)

For stdio-only clients:

{
  "mcpServers": {
    "chamade": {
      "command": "npx",
      "args": ["-y", "@chamade/mcp-server@3"],
      "env": {
        "CHAMADE_API_KEY": "chmd_..."
      }
    }
  }
}

Get an API key at https://chamade.io/dashboard.

Configuration

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows). Use Option A or B above.

Claude Code

.mcp.json at the root of your project. Use Option A (HTTP direct) for the best experience.

For real-time push events (transcripts, incoming DMs, ringing calls, WhatsApp dm_delivered flush), launch Claude Code with the channel flag every time:

claude --dangerously-load-development-channels server:chamade --continue

The flag is a per-launch client-side opt-in mandated by Claude Code for MCP channels not yet on the Anthropic allowlist — it's not dangerous, it's just the standard opt-in for experimental channels during the research preview. The server name after server: must match the key in your .mcp.json. Without the flag, tools still work but push events are silently ignored — you have to poll chamade_inbox and chamade_call_status to see new activity.

Cursor / Windsurf / OpenClaw

Same format. Path varies by client: .cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, ~/.openclaw/config.json. Use Option A if the client supports HTTP, otherwise Option B.

Tools

... View full README on GitHub