[BUG] MCP channel notifications not delivered to session (Discord/Telegram plugins)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Discord and Telegram channel plugins are installed and their MCP servers connect successfully, but messages sent through Discord/Telegram never arrive in the Claude Code session.
The MCP servers are calling mcp.notification({ method: 'notifications/claude/channel', ... }) to deliver messages, but Claude Code is not receiving these notifications.
The bot shows "typing..." indicator when messages are sent, but never replies because the notifications don't reach the session.
What Should Happen?
Messages from Discord/Telegram should automatically arrive in the Claude Code session as:
<channel source="discord" chat_id="..." message_id="..." user="..." ts="...">
This would allow Claude to receive and respond to messages automatically.
Error Messages/Logs
No errors shown. MCP servers show as "✓ Connected" in /mcp list.
The Discord server code successfully calls:
mcp.notification({
method: 'notifications/claude/channel',
params: { content, meta: { chat_id, message_id, ... } }
})
But these notifications never appear in the conversation.
Steps to Reproduce
- Install Discord or Telegram plugin: claude plugin install discord
- Configure bot token: /discord:configure <token>
- Enable Message Content Intent in Discord Developer Portal
- Approve pairing: /discord:access pair <code>
- Send message to bot via Discord DM
- Bot shows "typing..." but message never arrives in Claude Code session
- Can manually fetch with mcp__plugin_discord_discord__fetch_messages tool
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.81 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗