@chamade/mcp-server 1.1.1 → 1.1.3

package/README.md

@@ -54,7 +54,7 @@ Requires `CHAMADE_API_KEY` env var. Get one at https://chamade.io/dashboard.
 }
 ```
 
-### Claude Code
+### Claude Code (with channels — recommended)
 
 `.mcp.json` at the root of your project:
 
@@ -63,7 +63,7 @@ Requires `CHAMADE_API_KEY` env var. Get one at https://chamade.io/dashboard.
   "mcpServers": {
     "chamade": {
       "command": "npx",
-      "args": ["-y", "@chamade/mcp-server"],
+      "args": ["-y", "@chamade/mcp-server", "--channel"],
       "env": {
         "CHAMADE_API_KEY": "chmd_..."
       }
@@ -72,14 +72,16 @@ Requires `CHAMADE_API_KEY` env var. Get one at https://chamade.io/dashboard.
 }
 ```
 
-Claude Code supports **channel mode** — transcripts, messages, and incoming calls are pushed to the agent in real-time. No polling needed. The agent is notified automatically when someone speaks in the meeting or sends a DM.
-
-Channel mode currently requires starting Claude Code with development channels enabled:
+Then launch Claude Code with channels enabled:
 
 ```bash
-claude --dangerously-skip-permissions --dangerously-load-development-channels server:chamade
+claude --dangerously-load-development-channels server:chamade --continue
 ```
 
+This is required every session. The `--dangerously-load-development-channels` flag is standard Claude Code naming for loading third-party channels not yet on the official allowlist — it is not dangerous. `--continue` resumes the current conversation.
+
+With channel mode, transcripts, messages, and incoming calls are pushed to the agent in real-time — no polling needed.
+
 ### Cursor / Windsurf
 
 `.cursor/mcp.json` or `.windsurf/mcp.json` — same format as Claude Desktop.

package/dist/index.js

@@ -135,28 +135,35 @@ const BASE_INSTRUCTIONS = [
     "",
     "Per-platform defaults:",
     "- discord/teams: listen, speak, read, write, typing, files (full voice + chat)",
-    "- meet: listen, read, write (no TTS — use chamade_chat instead). Note: chat (read/write) only works for calendar-scheduled meetings. Ad-hoc Meet links have no chat API access.",
+    "- meet: listen, read, write (no TTS — use chamade_chat instead). Note: chat (read/write) only works for calendar-scheduled meetings. Ad-hoc Meet links have no chat API access. IMPORTANT: when the bot joins a Meet call, a participant in the meeting must manually accept it (Google shows a 'Someone wants to join' popup). Tell the user to accept the bot in the Meet UI.",
     "- zoom: listen, speak, read, write, files",
     "- telegram: read, write, typing, files (text DM only, no voice join)",
-    "- whatsapp: read, write, typing (text DM only, no voice join)",
+    "- whatsapp: read, write (text DM only, no voice join, no typing indicator)",
     "- sip: listen, speak (voice only, no chat)",
     "- nctalk: listen, speak, read, write, typing",
+    "- slack: read, write, files (text only, no voice — Huddles have no API)",
     "",
     "If 'speak' is not in capabilities, use chamade_chat to send text instead of chamade_say.",
     "",
     "## Platform requirements",
-    "Each platform requires specific setup by the user in the Chamade dashboard (https://chamade.io/dashboard):",
-    "- teams: Microsoft OAuth connection (for OnlineMeetings access)",
-    "- meet: Google OAuth connection (for Calendar API access)",
-    "- discord: a Discord bot token registered in the dashboard",
-    "- telegram: a Telegram bot token registered in the dashboard",
-    "- sip outbound: a SIP trunk connected in the dashboard (Pro plan required)",
-    "- sip inbound: a phone number (DID) activated in the dashboard — either répondeur (pool) or BYOT (own trunk)",
-    "- zoom/nctalk/whatsapp: just a meeting_url, no setup needed",
+    "Each platform requires specific setup. Use chamade_account to check what is already configured.",
+    "- teams: Microsoft OAuth connection (POST /api/oauth/start/microsoft)",
+    "- meet: Google OAuth connection (POST /api/oauth/start/google)",
+    "- discord: shared bot available by default. For DMs, user must connect via POST /api/oauth/start/discord. For voice, invite the shared bot to the server or register own bot via POST /api/bot-tokens.",
+    "- telegram: shared bot available by default. User must connect via POST /api/telegram/connect (returns a deeplink the user opens in Telegram).",
+    "- sip outbound: a SIP trunk connected via POST /api/sip/trunk (Pro plan required)",
+    "- sip inbound: a phone number (DID) activated via POST /api/sip/activate — either répondeur (pool) or BYOT (own trunk)",
+    "- slack: install shared app via POST /api/slack/install, or register own bot via POST /api/bot-tokens",
+    "- nctalk: Chamade Talk addon installed on the Nextcloud instance + connection via POST /api/nctalk/connect. Only the connected NC user can DM the bot; group rooms require /activate by the owner.",
+    "- zoom/whatsapp: just a meeting_url, no setup needed",
     "",
     "## Account status",
     "Use chamade_account to check platform readiness and remaining credit/quota before making calls.",
-    "Each platform shows: ok, not_configured (needs dashboard setup), or error (connection problem).",
+    "Platform statuses:",
+    "- 'ok (connected)' or 'ok (own bot)': fully set up, ready to use",
+    "- 'available (shared bot, user account not connected)': works via shared bot but user hasn't linked their account yet — ask if they want to connect",
+    "- 'not_configured': needs setup — tell the user what to do",
+    "- 'not_available': requires a plan upgrade",
     "",
     "## Common errors and what to tell the user",
     "- \"No discord bot registered\" → user needs to add a Discord bot token in the dashboard",
@@ -167,6 +174,10 @@ const BASE_INSTRUCTIONS = [
     "- \"SIP not available on free plan\" → user needs to upgrade to Pro for SIP calls",
     "- \"No SIP trunk configured\" → user needs to connect a SIP trunk in the dashboard for outbound SIP",
     "- \"Direct audio requires a Pro plan\" → direct audio streaming (raw PCM via WebSocket) is Pro only. Free users can still use chamade_say (TTS) within their voice quota",
+    "- \"Slack does not support voice calls\" → use chamade_inbox/chamade_send for Slack messaging instead",
+    "",
+    "## Account management",
+    `Chamade is fully bot-friendly. All account management (API keys, bot tokens, platform connections, SIP, billing) is available via the REST API at the same endpoints the dashboard uses. See ${CHAMADE_URL}/llms.txt for the full machine-readable documentation. This MCP server focuses on runtime operations (calls + messaging); use the REST API directly for account setup and configuration.`,
     "",
     "## Speech style",
     "- Speak naturally and concisely — your text is converted to speech.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chamade/mcp-server",
-  "version": "1.1.1",
+  "version": "1.1.3",
   "description": "MCP server for Chamade — voice gateway for AI agents. Join Discord, Teams, Meet, Telegram, SIP, Zoom meetings and interact via speech and text. Supports Claude Code channel mode for push events.",
   "type": "module",
   "bin": {
@@ -13,14 +13,7 @@
     "dev": "tsx src/index.ts",
     "test": "tsx test/run.ts"
   },
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/chamade/mcp-server.git"
-  },
   "homepage": "https://chamade.io",
-  "bugs": {
-    "url": "https://codeberg.org/skilpa/chamade/issues"
-  },
   "author": "Nafis <contact@nafis.io>",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.25.0",