telegram-sessions vs Telegram Agent by Nova (CIVAI)
telegram-sessions is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
telegram-sessions is a plugin bundle for AI coding tools published by bergamolt. No marketplace we read lists it any more. Telegram Agent by Nova (CIVAI) is an MCP server published by nova.civai.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Telegram Agent by Nova (CIVAI) | |
|---|---|---|
| Community marketplace bergamolt/telegram-sessions | Removed on 2026-10-19 Version: 0.4.2 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | telegram-sessionsno longer listed · | Telegram Agent by Nova (CIVAI) |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (nova.civai.co/mcp/agents/telegram-agent) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/bergamolt/telegram-sessions | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 25 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of telegram-sessions
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.
-
Connect a Telegram bot to your Claude Code session over MCP. The server logs in as a bot, forwards inbound messages into the session as <channel> notifications, and exposes tools…
-
Read a personal Telegram account over MTProto; every write is a plan a human applies.
-
This skill should be used for comprehensive Telegram automation via Telethon API. Use for sending/receiving messages, mo
-
Chatroost — unofficial Telegram MCP server
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account.
-
Local-first TDLib Telegram MCP server with 115 tools, account isolation and production guardrails.
What each says it does
telegram-sessions
Multi-session Telegram channel for Claude Code — daemon-based architecture with session routing, /new, /sessions, /kill commands from Telegram.
Telegram Agent by Nova (CIVAI)
I use your linked Telegram MTProto session (Integrations → Telegram) to list groups, members, and s…
How to run each
telegram-sessions
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Telegram Agent by Nova (CIVAI) As a remote MCP server
claude mcp add --transport http telegram-agent https://nova.civai.co/mcp/agents/telegram-agentCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Telegram Agent by Nova (CIVAI) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: telegram-sessions · What it can do: Telegram Agent by Nova (CIVAI) · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.