hdcd-telegram vs com.jojapi/telegram
hdcd-telegram is a plugin bundle for AI coding tools published by gohyperdev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.jojapi/telegram is an MCP server published by jojapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | hdcd-telegram | com.jojapi/telegram |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.jojapi.com/telegram) |
| 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 (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/gohyperdev/hdcd-telegram-plugin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
hdcd-telegram
Rust-based Telegram channel for Claude Code. Drop-in replacement for the official Bun-based Telegram plugin — same features, 20x lighter. 3.5 MB binary, ~5 MB RAM, <50ms startup. Includes access control (pairing, allowlists, group policies), voice transcription via Whisper, and all 4 MCP tools (reply, react, edit_message, download_attachment). Auto-downloads the correct binary for your platform on first use. Zero migration — reads existing token and access.json from the official plugin.
com.jojapi/telegram
Telegram: FASTEST real time Telegram API. Retrieve channel's info and messages in milliseconds..
How to run each
hdcd-telegram
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.jojapi/telegram As a remote MCP server
claude mcp add --transport http telegram https://mcp.jojapi.com/telegramCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.jojapi/telegram 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: hdcd-telegram · What it can do: com.jojapi/telegram · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.