[BUG] Telegram MCP server disconnects silently after idle period

Resolved 💬 2 comments Opened Mar 20, 2026 by 0xsaltylollipop Closed Apr 18, 2026

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?

Long-running MCP servers (e.g. the Telegram plugin) get disconnected after a period of inactivity without any user action. The server process appears to be reaped or the stdio pipe is closed. Reconnecting via /mcp resolves it until the next idle period.

What Should Happen?

Telegram MCP servers should stay connected for the lifetime of the Claude Code session, regardless of idle time on the stdio pipe.

Error Messages/Logs

Steps to Reproduce

  1. Connect a long-polling MCP server (Telegram channel plugin)
  2. Send/receive a few messages successfully
  3. Wait ~5-10 minutes with no interaction
  4. Send another message from Telegram → no response, server is disconnected
  5. Run /mcp to reconnect → works again

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.80

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗