telegram-report vs Telegram Bridge
telegram-report is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
telegram-report is a plugin bundle for AI coding tools published by Jongwon Choi. No marketplace we read lists it any more. Telegram Bridge is an MCP server published by antonio-castellon. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 Bridge | |
|---|---|---|
| Community marketplace jongwony/cc-plugin | Removed on 2026-10-26 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 Downloads/month (PyPI): 448 Downloads/week (PyPI): 208 Forks (GitHub): 0 Stars (GitHub): 0 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-reportno longer listed · | Telegram Bridge |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 11 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-27 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (mcp-telegram-bridge) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jongwony/cc-plugin | github.com/antonio-castellon/mcp-telegram-bridge |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-23 | 2026-10-11 |
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-report
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Run a Telegram channel from your AI agent. Posts go out through your own bot, not your account.
-
Full-spectrum Telegram access for coding agents through the tg-agent CLI: channels, chats, messages, media, admin, content pipelines, analytics.
-
This skill should be used for comprehensive Telegram automation via Telethon API. Use for sending/receiving messages, mo
-
Telegram messaging bridge with built-in access control. Manage pairing, allowlists, and policy via /telegram:access.
-
Telegram channels you administer: analytics, content plans, scheduled publishing. No userbot
-
telegram com.jojapi/telegram
Telegram: FASTEST real time Telegram API. Retrieve channel's info and messages in milliseconds..
What each says it does
telegram-report
Send-only Telegram report for scheduled routines — posts one message into a fixed forum topic by thread id, with credentials from TELEGRAM_BOT_TOKEN / TELEGRAM_CHAT_ID; never creates topics or reads updates
Telegram Bridge
Stdio MCP bridge to Telegram with scrubbing and a fail-closed allowlist.
How to run each
telegram-report
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Telegram Bridge As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-telegram-bridge -- uvx mcp-telegram-bridgeCommands built only from what the marketplaces declare; the full set for every client is on each card.
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-report · What it can do: Telegram Bridge · 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.