Chamade MCP server
✓ 인증됨AI agent이 Discord, Teams, Slack, WhatsApp 등의 음성 회의 및 채팅에 참여할 수 있도록 지원합니다.
다른 이름 chamade-io/mcp-server, mcp-server, @chamade/mcp-server
- 스타
- 0
- Tools
- 14
- 다운로드, 30일
- 377
- 최신 버전
- 5.1.0
- 마지막 커밋
- 2026년 6월 4일
- 라이선스
- MIT
Chamade MCP란?
AI agent이 Discord, Teams, Slack, WhatsApp 등의 음성 회의 및 채팅에 참여할 수 있도록 지원합니다. 14개 도구를 제공합니다. 예: chamade_call_join, chamade_call_say, chamade_call_chat.
프로젝트 README에서 생성된 요약
Chamade MCP server 정보
Chamade는 AI agent가 다양한 플랫폼에서 음성 회의 및 텍스트 대화에 참여할 수 있도록 돕는 커뮤니케이션 게이트웨이 역할을 합니다. Discord, Microsoft Teams, Google Meet, Telegram, Slack, WhatsApp, Zoom, Nextcloud Talk, SIP 등 광범위한 서비스를 지원합니다. 개발자는 이 서버를 사용하여 agent가 통화에 참여하고, 채팅 메시지를 보내며, 다이렉트 메시지를 관리하도록 설정할 수 있습니다. 시스템은 텍스트 기반으로 설계되었으며, agent는 도구를 통해 상호작용하고 서버는 음성 처리와 같은 복잡한 작업을 수행합니다.
사용자는 Claude Desktop 또는 Cursor와 같은 클라이언트를 위해 호스팅된 HTTP 전송 방식을 선택하거나, 이전 버전의 클라이언트를 위해 stdio shim을 사용할 수 있습니다. 음성 기능의 경우, ElevenLabs, Deepgram, OpenAI, Cartesia와 같은 서비스의 API key를 직접 제공하는 호스팅 음성 파이프라인을 지원합니다. 또는 개발자가 WebSockets를 통해 직접 raw-PCM 오디오를 제공할 수도 있습니다. 또한 서버는 지원되는 플랫폼에 대한 파일 전송을 관리하며, agent가 전용 업로드 도구를 통해 최대 25 MB까지 첨부 파일을 주고받을 수 있도록 지원합니다.
활용 사례
- 1회의 참여 및 발언AI agent가 음성 통화에 입장하여 text-to-speech 기술을 사용하여 말할 수 있습니다.
- 2멀티 플랫폼 다이렉트 메시지 관리개발자가 agent에게 Discord, WhatsApp 또는 Telegram의 개인 메시지를 확인하고 응답하도록 지시할 수 있습니다.
- 3채팅 내 파일 첨부 처리agent가 보안 업로드 URL을 생성하여 대화에 파일을 업로드할 수 있습니다.
- 4실시간 회의 트랜스크립트 모니터링AI가 실시간 트랜스크립트 업데이트를 읽음으로써 진행 중인 대화를 추적할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Chamade MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Chamade MCP 설치
$ claude mcp add mcp-server -- npx -y @chamade/mcp-serverCursor에 Chamade MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}VS Code에 Chamade MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}VS Code CLI에 Chamade MCP 설치
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@chamade/mcp-server"]}'Claude Desktop에 Chamade MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}Codex에 Chamade MCP 설치
$ codex mcp add mcp-server -- npx -y @chamade/mcp-serverCodex config.toml에 Chamade MCP 설치
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@chamade/mcp-server"]
Gemini CLI에 Chamade MCP 설치
$ gemini mcp add -s user mcp-server npx -- -y @chamade/mcp-serverGemini settings.json에 Chamade MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@chamade/mcp-server"
]
}
}
}Chamade MCP 도구 14
README에서 감지됨chamade_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 | — |
도구 14개 모두 보기도구 수 줄이기
chamade_file_upload_urlchamade_account
| chamade_file_upload_url | — | |
| chamade_account | — |
구성
CHAMADE_API_KEY
| 이름 | 설명 | 유형 |
|---|---|---|
| CHAMADE_API_KEY | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능chamade-io/mcp-server is public and reachablegithub.com/chamade-io/mcp-server ↗통과
- 패키지가 이 저장소를 소스로 명시@chamade/mcp-server names chamade-io/mcp-server as sourcenpmjs.com/package/@chamade/mcp-server ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-07-23github.com/chamade-io/mcp-server ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @chamade/mcp-server통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음87 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음14 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
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.
Chamade MCP 질문
Chamade MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add mcp-server -- npx -y @chamade/mcp-server를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Chamade MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Chamade MCP는 어떤 도구를 제공하나요?
14개 도구를 제공합니다. 예: chamade_call_join, chamade_call_say, chamade_call_chat, chamade_call_status, chamade_call_accept.
AI agent의 음성 처리는 어떻게 하나요?
대시보드에 ElevenLabs 또는 OpenAI와 같은 API key를 입력하여 Chamade의 호스팅 STT/TTS를 사용하거나, raw-PCM 오디오 WebSocket을 사용하여 직접 음성 레이어를 구현할 수 있습니다.
agent가 채팅에서 파일을 보낼 수 있나요?
네, Discord, Telegram, Slack, WhatsApp, Nextcloud Talk에서 파일 첨부가 가능합니다. 파일 업로드 도구를 사용하여 업로드용 pre-signed URL을 생성할 수 있습니다.
서버가 실시간 푸시 이벤트를 지원하나요?
네, 'channel mode'를 통해 DM, 트랜스크립트, 통화 상태를 agent에게 직접 푸시합니다. Claude Code에서 이 기능을 사용하려면 특정 플래그가 필요합니다.
이 서버는 어떤 인증 방식을 사용하나요?
서버 사용을 위해 'chmd_'로 시작하는 Chamade API key가 필요합니다.