Telegram plugin MCP server disconnects immediately after startup

Resolved 💬 3 comments Opened Apr 4, 2026 by maker-KK Closed Apr 8, 2026

Description

The Telegram plugin MCP server process starts but is not maintained by Claude Code. The server disconnects almost immediately after initialization, preventing any Telegram messages from being received.

Environment

  • Claude Code: 2.1.92
  • macOS (Darwin 25.4.0)
  • Bun: 1.3.11
  • Plugin: telegram@claude-plugins-official v0.0.4

Reproduction

  1. Install the Telegram plugin from claude-plugins-official marketplace
  2. Configure bot token in ~/.claude/channels/telegram/.env
  3. Start a Claude Code session
  4. The plugin MCP server appears in /reload-plugins output but immediately disconnects
  5. ps aux | grep telegram shows no running plugin process
  6. System reminder appears: "The following MCP servers have disconnected: plugin:telegram:telegram"

Diagnosis

Manual testing confirms the plugin itself works perfectly:

# Manual test with FIFO to simulate Claude Code's MCP connection:
mkfifo /tmp/tg_fifo
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}' > /tmp/tg_fifo &
bun run --cwd ~/.claude/plugins/cache/claude-plugins-official/telegram/0.0.4 --shell=bun --silent start < /tmp/tg_fifo 2>&1

Result: telegram channel: polling as @<botname> — process stays alive and polls successfully.

However, when Claude Code spawns the MCP server process, it either:

  • Closes stdin prematurely, causing the StdioServerTransport to shut down
  • Kills the process shortly after initialization
  • Fails to maintain the MCP connection

Key evidence:

  • getWebhookInfo returns "url": "" (no webhook set — expected, plugin uses long polling)
  • getUpdates returns 200 OK with no 409 conflict — confirming nothing is polling
  • Plugin configuration (token, access.json, settings.json) is all correct
  • Clearing plugin cache and restarting does not help
  • Multiple session restarts and /reload-plugins do not resolve the issue

Expected Behavior

The Telegram MCP server should remain connected and actively polling for the duration of the Claude Code session.

Actual Behavior

The MCP server initializes successfully but disconnects within seconds. No Telegram messages can be received.

🤖 Generated with Claude Code

View original on GitHub ↗

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