
Chamade
Let your coding agent join voice and chat on Discord, Slack, Teams, Zoom, Telegram, WhatsApp, Meet, NC Talk, and SIP from one MCP surface.
Overview
io.chamade/server is a MCP server for the Build phase that gives AI agents unified voice and chat across Discord, Teams, Meet, Slack, Zoom, Telegram, WhatsApp, NC Talk, and SIP.
What is this MCP server?
- Registry v4.0.0 with npm package @chamade/mcp-server and stdio transport
- 9 channel families: Discord, Teams, Meet, Slack, Zoom, Telegram, WhatsApp, NC Talk, SIP
- Hosted remote https://mcp.chamade.io/mcp/ with Bearer chmd_* API key or OAuth 2.1 DCR + PKCE
- Open-source server at github.com/chamade-io/mcp-server
- Registry version 4.0.0
- 9 communication surfaces in registry description
- 2 transports: streamable-http remote + npm stdio @chamade/mcp-server v4.0.0
What problem does it solve?
Shipping an agent that must talk on many chat and voice platforms forces solo builders into a maze of webhooks, tokens, and SDKs.
Who is it for?
Indie builders building agent-first products, community bots, or multi-channel support without staffing a integrations team.
Skip if: Static documentation sites, teams that only need email, or environments that cannot store Bearer or OAuth credentials securely.
What do I get? / Deliverables
One Chamade MCP registration lets the agent send, receive, and coordinate across major comms channels from your existing coding agent.
- Agent-reachable messaging and voice across listed channels
- Reduced bespoke webhook code per platform
- Faster multi-channel agent MVP
Recommended MCP Servers
Journey fit
Chamade’s primary shelf is Build agent-tooling because you register channels while constructing the agent product, even though you also use it to ship and support users. Agent-tooling fits a dedicated MCP server that extends where the agent can listen and reply across many comms protocols.
How it compares
Multi-channel comms MCP bridge, not a CRM skill or a single-platform Discord-only bot template.
Common Questions / FAQ
Who is io.chamade/server for?
It is for builders running AI agents who need voice and chat on Discord, Slack, Teams, Zoom, Telegram, WhatsApp, Meet, NC Talk, or SIP through MCP.
When should I use io.chamade/server?
Use it while building or operating an agent that must participate in live channels instead of wiring each platform separately.
How do I add io.chamade/server to my agent?
Sign up at chamade.io for a chmd_* key, add Authorization Bearer to the https://mcp.chamade.io/mcp/ remote, or use OAuth 2.1 DCR; alternatively install @chamade/mcp-server for stdio.