holla vs telegram
holla is a plugin bundle for AI coding tools published by Circles Inc.. Marketplaces we read that list it: 1 (Community GitHub marketplaces). telegram is a plugin bundle for AI coding tools published by mjavadalavi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-17. 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 |  telegram | |
|---|---|---|
| Community marketplace circlesac/holla-cli | Listed Version: not stated Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: not stated 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 | holla | telegram |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/circlesac/holla-cli | github.com/mjavadalavi/claude-plugins-official |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-12 |
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
holla
Operate holla across messaging providers, with Slack commands, gotchas, and verification
telegram
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 to reply (with attachments up to 50MB), react with emoji, edit prior messages, and download inbound files. Built-in access control supports DM pairing flows and group/supergroup allowlists managed through the /telegram:access skill. Forum-topic routing via TELEGRAM_TOPIC_IDS lets a single bot fan out to multiple parallel Claude Code sessions, each bound to its own supergroup topic, so four sessions can work on four projects without racing for inbound messages. Proxy-aware transport (TELEGRAM_PROXY / HTTPS_PROXY) routes both text and multipart uploads through an HTTP proxy for use in regions where api.telegram.org is blocked or rate-limited.
How to run each
holla As a Claude Code plugin
/plugin marketplace add circlesac/holla-cli
/plugin install holla@hollatelegram As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install telegram@claude-communityCommands 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: holla · What it can do: telegram · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.