Chamade MCP server

@chamade/mcp-server

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

The recommended voice path is hosted STT/TTS with bring-your-own-key. Drop your own ElevenLabs / Deepgram / OpenAI / Cartesia API key in your dashboard once — Chamade runs the full speech pipeline on its side using that key. Transcripts flow in as calltranscript events, chamadecall_say speaks into the meeting. Free on Chamade's side; you only pay your provider. Your agent stays fully text-driven.

Already have a voice pipeline you want to keep (OpenAI Realtime, LiveKit Agents, Pipecat, Deepgram Voice Agent, a manual cascade)? Chamade also exposes the call's raw-PCM audio as a bidirectional WebSocket — BYO audio, Chamade transports, you run the speech layer. Either mode, same MCP tools for control.

File attachments work out of the box on DMs and meeting chat for Discord, Telegram, Slack, WhatsApp (incl. voice notes), and Nextcloud Talk. Use chamadefileuploadurl to mint a pre-signed no-auth upload URL, then pass the returned fileid in attachments on chamadedmchat or chamadecallchat. Inbound files arrive on chamade_inbox as Chamade-signed URLs — your agent can curl them with no extra auth. Teams + Meet support is code-ready but gated until the respective platform certifications complete.

Chamade is currently in early access: free, no subscription, no quota.

v4: 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.

What changed in v4

v4 is a server-side wire-shape change picked up automatically by the shim. Headline items, full detail in docs/AGENTS.md:

• Channels are now Agents. Per-bearer scoping is unchanged; the noun is agent everywhere on the wire and in tool descriptions.
• accountid is the canonical join key. Used identically in chamadedmchat, chamadecall_join, event payloads, and reply XML tag attributes.
• Event payload v2. data carries accountid + from + fromname (sender fields removed) and a pre-stuffed agentcontext.{accounts, active_calls} snapshot so the agent always knows what it's on without an extra round-trip.
• Explicit-target XML tags. Reply XML can now address conversations / calls outside the current reply context (, , …) for cross-target initiation.
• Auto-MCP attachment. Providers with native MCP-as-tool support (OpenAI Responses, Anthropic Managed Agents, Foundry) receive the Chamade MCP server pre-injected with a per-agent bearer.

Shortened. The full README is on GitHub.