Channel plugin MCP tools not exposed to model session

Bug

Telegram channel plugin's MCP tools (reply, react, edit_message) are not registered in the model's available
tool list, making the channel effectively one-way (inbound only).

Environment

• Claude Code on Windows 11 (bash shell)
• Bun 1.3.11
• Plugin: telegram@claude-plugins-official v0.0.1
• Session started with: claude --channels plugin:telegram@claude-plugins-official

What works

• Plugin enabled in ~/.claude/settings.json (enabledPlugins)
• Token set in ~/.claude/channels/telegram/.env
• access.json configured (allowlist mode, user ID whitelisted)
• Server starts successfully, polls Telegram (telegram channel: polling as @WARRIGBRAIN_BOT)
• Bot receives DMs, inbound gate passes, MCP notification reaches the model
• Direct curl to Telegram Bot API sendMessage delivers messages fine

What fails

• ToolSearch for "telegram", "reply", "react", "channel" returns zero telegram-related tools
• The tools registered via ListToolsRequestSchema in server.ts never appear in the model's deferred or loaded

tool list

• Model generates a response in the terminal but has no reply tool to call, so responses never reach Telegram
• Reloading plugin (/reload-plugins) and restarting sessions does not fix it

Expected

The channel plugin's MCP tools should be callable by the model, same as any other MCP server's tools.

Workaround

Sending messages via curl through the Bash tool works, but bypasses the plugin's access control and chunking
logic.