Repository navigation
v0.4.2
Fixes the bug that made the hosted connector unusable.
A server instance is now built per session. One McpServer was connected to every new transport, which the SDK refuses, so the process crashed the moment a client opened a second session. A hand-run curl only ever opens one, which is why it passed every test and returned 502s against a real client.
Also in 0.4.1: a bare GET answers 405 rather than 400, so clients probing the endpoint before opening a session no longer read it as "not an MCP server".
| Profile | Tools | Every turn |
|---|---|---|
core (default) |
13 | 2,218 |
read |
31 | 4,673 |
full |
74 | 11,643 |
npm install -g @thenavidm/telegram-mcp-cliFull Changelog: v0.4.0...v0.4.2