Telegram channel MCP server disconnects after 5s, drops messages

Bug

The Telegram channel plugin (v0.0.4) MCP server cleanly disconnects after ~5s of inactivity, making the channel unusable for ongoing conversation. After every single message exchange, the bot dies and requires manual /mcp reconnection.

Debug log

MCP server "plugin:telegram:telegram": UNKNOWN connection closed after 5s (cleanly)
MCP server "plugin:telegram:telegram": Cleared connection cache for reconnection

The server connects on-demand, successfully calls the reply tool, then immediately shuts down:

MCP server "plugin:telegram:telegram": Starting connection with timeout of 30000ms
MCP server "plugin:telegram:telegram": Successfully connected (transport: stdio) in 134ms
MCP server "plugin:telegram:telegram": Calling MCP tool: reply
MCP server "plugin:telegram:telegram": Tool 'reply' completed successfully in 430ms
...
MCP server "plugin:telegram:telegram": UNKNOWN connection closed after 5s (cleanly)

Also seeing repeated Tool mcp__plugin_telegram_telegram__reply not found errors because the server isn't connected when Claude tries to call it (deferred/lazy-loaded).

Expected behavior

Channel MCP servers should remain persistent for the lifetime of the Claude Code session, since they need to listen for incoming messages continuously.

Reproduction

1. claude --channels plugin:telegram@claude-plugins-official --debug
2. Send a message from Telegram
3. Bot replies once, then disconnects after ~5s
4. Next Telegram message is never received

Environment

• Claude Code: 2.1.98
• Telegram plugin: 0.0.4
• macOS, Bun runtime