MCP server de Chamade
✓ VerificadoPermite que los agentes de IA se unan a reuniones de voz y chateen en Discord, Teams, Slack, WhatsApp y más.
También conocido como chamade-io/mcp-server, mcp-server, @chamade/mcp-server
- Stars
- 0
- Herramientas
- 14
- Descargas, 30 días
- 377
- Última versión
- 5.1.0
- Último commit
- 4 jun 2026
- Licencia
- MIT
¿Qué es Chamade MCP?
Permite que los agentes de IA se unan a reuniones de voz y chateen en Discord, Teams, Slack, WhatsApp y más. Expone 14 herramientas, como chamade_call_join, chamade_call_say, chamade_call_chat.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Chamade
Chamade actúa como una pasarela de comunicación que permite a los agentes de IA participar en reuniones de voz y conversaciones de texto en diversas plataformas. Es compatible con una amplia gama de servicios, incluyendo Discord, Microsoft Teams, Google Meet, Telegram, Slack, WhatsApp, Zoom, Nextcloud Talk y SIP. Los desarrolladores pueden usar este servidor para permitir que los agentes se unan a llamadas, envíen mensajes de chat y gestionen mensajes directos. El sistema está diseñado para ser impulsado por texto, donde el agente interactúa mediante herramientas mientras el servidor se encarga del procesamiento pesado del habla.
Los usuarios pueden elegir entre un transporte HTTP alojado para clientes como Claude Desktop o Cursor, o usar un shim de stdio para clientes más antiguos. Para capacidades de voz, el servidor admite un pipeline de voz alojado donde proporcionas tus propias API keys para servicios como ElevenLabs, Deepgram, OpenAI o Cartesia. Alternativamente, los desarrolladores pueden proporcionar su propio audio raw-PCM a través de WebSockets. El servidor también gestiona la transferencia de archivos para las plataformas compatibles, permitiendo que los agentes envíen y reciban archivos adjuntos de hasta 25 MB mediante herramientas de subida especializadas.
Qué puedes hacer con él
- 1Unirse y hablar en reunionesUn agente de IA puede entrar en una llamada de voz y hablar utilizando tecnología text-to-speech.
- 2Gestionar mensajes directos multiplataformaUn desarrollador puede instruir a un agente para que revise y responda a mensajes privados en Discord, WhatsApp o Telegram.
- 3Gestionar archivos adjuntos en el chatUn agente puede subir archivos a una conversación generando una URL de subida segura.
- 4Monitorear transcripciones de reuniones en vivoUna IA puede seguir una conversación en vivo leyendo las actualizaciones de las transcripciones en tiempo real.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Chamade MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Chamade MCP en Claude Code
$ claude mcp add mcp-server -- npx -y @chamade/mcp-serverInstalar Chamade MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}Instalar Chamade MCP en VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}Instalar Chamade MCP en VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@chamade/mcp-server"]}'Instalar Chamade MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}Instalar Chamade MCP en Codex
$ codex mcp add mcp-server -- npx -y @chamade/mcp-serverInstalar Chamade MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@chamade/mcp-server"]
Instalar Chamade MCP en Gemini CLI
$ gemini mcp add -s user mcp-server npx -- -y @chamade/mcp-serverInstalar Chamade MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}Herramientas de Chamade MCP 14
Detectado desde el READMEchamade_call_joinchamade_call_saychamade_call_chatchamade_call_statuschamade_call_acceptchamade_call_refusechamade_call_typingchamade_call_leavechamade_call_listchamade_inboxchamade_dm_chatchamade_dm_typing
| chamade_call_join | — | |
| chamade_call_say | — | |
| chamade_call_chat | — | |
| chamade_call_status | — | |
| chamade_call_accept | — | |
| chamade_call_refuse | — | |
| chamade_call_typing | — | |
| chamade_call_leave | — | |
| chamade_call_list | — | |
| chamade_inbox | — | |
| chamade_dm_chat | — | |
| chamade_dm_typing | — |
Mostrar las 14 herramientasMostrar menos herramientas
chamade_file_upload_urlchamade_account
| chamade_file_upload_url | — | |
| chamade_account | — |
Configuración
CHAMADE_API_KEY
| Nombre | Descripción | Tipo |
|---|---|---|
| CHAMADE_API_KEY | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblechamade-io/mcp-server is public and reachablegithub.com/chamade-io/mcp-server ↗Aprobado
- El paquete indica este repositorio como su origen@chamade/mcp-server names chamade-io/mcp-server as sourcenpmjs.com/package/@chamade/mcp-server ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-07-23github.com/chamade-io/mcp-server ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @chamade/mcp-serverAprobado
- No hay avisos críticos en el paquete ni en sus dependencias87 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo14 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en GitHub@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 call_transcript events, chamade_call_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 chamade_file_upload_url to mint a pre-signed no-auth upload URL, then pass the returned file_id in attachments on chamade_dm_chat or chamade_call_chat. 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-remoteunder 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
agenteverywhere on the wire and in tool descriptions. account_idis the canonical join key. Used identically inchamade_dm_chat,chamade_call_join, event payloads, and reply XML tag attributes.- Event payload v2.
datacarriesaccount_id+from+from_name(sender_* fields removed) and a pre-stuffedagent_context.{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 (
<dm platform=…>,<call_say call_id=…>, …) 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.
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_..."
}
}
}
}
CHAMADE_API_KEY is required. Get a real one at https://chamade.io/dashboard → API keys and paste the full chmd_… value (≥ 40 chars after the prefix). If the env var is missing, empty, or still contains a placeholder like chmd_..., the shim refuses to start instead of silently falling back to OAuth — that fallback path loops on refresh-and-revoke and is not a viable auth method for this server.
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
| Tool | Description |
|---|---|
chamade_call_join |
Join a voice meeting (platform + meeting_url). |
chamade_call_say |
Speak text aloud via TTS in the meeting. |
chamade_call_chat |
Send a text chat message in the meeting. Optional attachments: [{file_id} | {url} | {bytes_b64, name, mime}] to send files along with the text; text becomes the caption when both are set. 25 MB cap per attachment. |
chamade_call_status |
Get call state and new transcript lines (delta pattern). |
chamade_call_accept |
Answer a ringing inbound call (SIP, etc.). |
chamade_call_refuse |
Refuse/reject a ringing inbound call. |
chamade_call_typing |
Send a typing indicator in meeting chat. |
chamade_call_leave |
Hang up and leave the meeting. |
chamade_call_list |
List all active calls. |
chamade_inbox |
Check DM conversations (Discord, Telegram, Teams, WhatsApp, Slack, NC Talk). Shows WhatsApp 24h window state inline. Inbound file attachments arrive as attachments[] on each message, with Chamade-signed URLs. |
chamade_dm_chat |
Send a DM message by platform. Optional attachments: [{file_id} | {url} | {bytes_b64, name, mime}] to send files; text becomes the caption. On WhatsApp outside the 24h window, returns 202 queued and auto-fires a re-engagement template. |
chamade_dm_typing |
Send a typing indicator in DM by platform. |
chamade_file_upload_url |
Mint a short-lived (5 min) pre-signed upload URL. Your shell / agent curl -F file=@path <url> with no auth header (URL itself is the auth), then pass the returned file_id in attachments: [{file_id}] on a subsequent send. Recommended path for any non-trivial local file — a shell-streamed upload keeps the tool call tiny instead of forcing every base64 character through the model's output budget. |
chamade_account |
Check account status, plan, credit/quota, and per-platform readiness (incl. a files bool per platform). |
Resources
| URI template | Description |
|---|---|
chamade://calls/{call_id}/transcript |
Live transcript. Each read returns only new lines since the last read (delta pattern). Channel-mode clients also receive push notifications for every new line. |
Channel mode (push events)
Channel mode pushes DM messages, incoming SIP calls, transcript lines, call state changes, and WhatsApp dm_delivered flush events directly into the agent's context — no polling.
Server side — nothing to configure. The hosted Chamade MCP server always declares the experimental.claude/channel capability during the initialize handshake. The v2.x --channel arg / CHAMADE_CHANNEL=1 env var are gone.
Client side — Claude Code needs a per-launch flag. Claude Code only processes notifications/claude/channel from MCP servers you've explicitly opted in:
claude --dangerously-load-development-channels server:chamade --continue
Required every launch. Without it, Chamade tools still work but push events are silently dropped client-side — the agent has to poll chamade_inbox and chamade_call_status to see new activity.
Other MCP clients (Claude Desktop, Cursor, Windsurf) currently do not have a channel receiver and will silently ignore push notifications. They still work in polling mode via chamade_inbox with last_message_cursor + optional wait for long-polling.
Environment variables (shim only)
Only the stdio shim uses these. Direct HTTP config has everything in JSON.
| Variable | Required | Default | Description |
|---|---|---|---|
CHAMADE_API_KEY |
Yes | — | API key (chmd_*, ≥ 40 chars of entropy) from chamade.io/dashboard. The shim validates the shape at startup and exits 1 on placeholders or missing values; there is no OAuth fallback. |
CHAMADE_URL |
No | https://chamade.io |
Chamade instance URL. The shim derives the MCP endpoint automatically: https://chamade.io → https://mcp.chamade.io/mcp/, https://dev.chamade.io → https://mcp.dev.chamade.io/mcp/. |
CHAMADE_MCP_URL |
No | — | Explicit MCP endpoint override. Skip unless you're running a custom proxy. |
The v2.x --channel CLI flag is silently accepted for backwards-compat, but it's a no-op — channel mode is always on in v3.
Supported platforms
- Discord — voice channels (shared bot or bring your own), text, files (send + receive, 25 MB)
- Microsoft Teams — voice meetings + text DM, requires OAuth connection on dashboard. Files code-ready, gated behind AppSource cert.
- Google Meet — voice (audio_in) + chat text, requires OAuth connection on dashboard (see note below). Files code-ready, gated behind Google OAuth verification.
- Telegram — DM text + files (send + receive). No voice.
- Zoom — voice + meeting chat, pass meeting URL (pending Zoom Marketplace approval — tester access on request). No files.
- SIP / Phone — voice only, pass phone number or SIP URI. No files.
- Nextcloud Talk — voice + text + files (send on any addon version, receive needs addon ≥ 2.4.0)
- WhatsApp — DM text + files (send + receive, incl. voice notes as raw audio). No voice calls.
⚠️ Google Meet voice — beta limitation. Real-time audio capture on Meet relies on Google's Meet Media API, currently in Developer Preview. Every meeting participant must be individually enrolled — if anyone isn't, audio capture fails. Calendar integration and in-meeting chat work normally for everyone. For production voice use cases, prefer Teams, Discord, Nextcloud Talk, or SIP.
How it works
Agent (Claude Desktop, Cursor, …)
│ MCP (Streamable HTTP, Authorization: Bearer chmd_*)
▼
mcp.chamade.io (hosted by Chamade)
│
▼
Chamade API (chamade.io)
│
▼
Maquisard bridge (transports audio; forwards to your
STT/TTS provider when BYOK preset set)
│
▼
Discord / Teams / Meet / …
With Option B (stdio shim), the client doesn't speak HTTP; the shim sits in between as a transport adapter:
Agent (stdio-only client)
│ stdio JSON-RPC
▼
@chamade/mcp-server@3 (this package, ~160 LOC)
│ spawns
▼
mcp-remote (local subprocess)
│ Streamable HTTP, Bearer chmd_*
▼
mcp.chamade.io (hosted)
Development
npm install
npm run dev # runs with tsx (hot reload, src/index.ts)
npm run build # compiles to dist/
npm test # unit tests for deriveMcpUrl + buildRemoteArgs
The shim itself is tiny (see src/index.ts). Full MCP tool behavior is tested in the parent Chamade repo under tests/e2e/test_mcp_http.py, which drives the hosted server directly — that's the source of truth for tool semantics.
Documentation
- MCP server docs — setup for every major client
- Push mode docs — how real-time push events work (stateful sessions)
- Agents — bearer × platform scoping (one agent per key / OAuth client)
- Full API reference — every tool, every endpoint, LLM-formatted
- Setup guide — step-by-step onboarding for agents
Issues & feedback
- Bug or feature request: open an issue
- Direct contact: contact@nafis.io
- In-app: every Chamade dashboard has a "Send feedback" button
License
MIT — see LICENSE.
Preguntas sobre Chamade MCP
¿Cómo agrego Chamade MCP a Claude Code?
Ejecuta claude mcp add mcp-server -- npx -y @chamade/mcp-server en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Chamade MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona Chamade MCP?
Expone 14 herramientas, incluidas chamade_call_join, chamade_call_say, chamade_call_chat, chamade_call_status, chamade_call_accept.
¿Cómo gestiono la voz de mi agente de IA?
Puedes usar el STT/TTS alojado de Chamade proporcionando tus propias API keys (como ElevenLabs o OpenAI) en el dashboard, o usar el WebSocket de audio raw-PCM para ejecutar tu propia capa de voz.
¿Puede mi agente enviar archivos en los chats?
Sí, los archivos adjuntos funcionan en Discord, Telegram, Slack, WhatsApp y Nextcloud Talk. Puedes usar la herramienta de subida de archivos para obtener una URL pre-firmada para las cargas.
¿El servidor admite eventos push en tiempo real?
Sí, mediante el 'channel mode', que envía DMs, transcripciones y estados de llamada directamente al agente. Claude Code requiere un flag específico para habilitar esto.
¿Qué método de autenticación utiliza este servidor?
El servidor requiere una API key de Chamade que comience con 'chmd_'.