Telegram plugin: MCP connection drops after first inbound message

Description

The Telegram channel plugin (telegram@claude-plugins-official v0.0.1) disconnects from the MCP stdio transport immediately after delivering the first inbound message to the Claude Code session.

Reproduction

1. Configure Telegram plugin, pair a sender via /telegram:access pair <code>
2. Send a message from Telegram — it arrives in the session correctly
3. Reply works fine (outbound via reply tool succeeds)
4. Send a second message from Telegram — it never arrives
5. The MCP tools (mcp__plugin_telegram_telegram__reply) become unavailable (tool not found)
6. Running /mcp reconnects successfully, but the cycle repeats on the next inbound message

Expected behavior

The MCP connection should remain stable across multiple inbound messages without requiring manual /mcp reconnects.

Observed behavior

• First inbound notifications/claude/channel is delivered successfully
• Connection drops immediately after — subsequent notifications never reach the session
• Outbound tools disappear from the tool list
• /mcp reconnect fixes it, but only for one more message

Environment

• Claude Code CLI (latest)
• Telegram plugin v0.0.1 (telegram@claude-plugins-official)
• Linux (Ubuntu)
• Plugin server: Bun + @modelcontextprotocol/sdk stdio transport

Related issues

• #36431
• #36472
• #29549

🤖 Generated with Claude Code