Ext Ops Panel
Open dashboard
Comparison

telegram-per-project vs Better-TG-CLI (Telegram)

telegram-per-project is a plugin bundle for AI coding tools published by trezero. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Better-TG-CLI (Telegram) is an MCP server published by TheVilfer. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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

Where each is published
Marketplacetelegram-per-projectBetter-TG-CLI (Telegram)
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.37.0
Downloads/month (npm): 5 157
Downloads/week (npm): 964
Forks (GitHub): 4
Stars (GitHub): 3
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

telegram-per-project vs Better-TG-CLI (Telegram)
Facttelegram-per-projectBetter-TG-CLI (Telegram)
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleOn your machine (better-tg-cli)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 01, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)4Not a bundle
LicenceMITMIT
Repository (differs)github.com/trezero/telegram-per-projectgithub.com/thevilfer/better-tg-cli
Changes in the last 7 days (differs)07
First seen (differs)2026-10-122026-10-11

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

telegram-per-project

In its own words, on Claude Code: claude-plugins-community:

Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach Terminal 1 and messages to @beta_bot reach Terminal 2, with no cross-talk. Key features: - Per-project bot tokens via TELEGRAM_PROJECT_ID environment variable - Independent access policies per project, bootstrapped from global config - Response timeout — notifies senders when the assistant isn't responding (configurable, default 45s) - Full access control: DM pairing, allowlists, group mention detection - Reply, react, and edit_message tools for the assistant - Photo support with inline preview - Fully backward compatible — works as a single global bot if no project ID is set

Better-TG-CLI (Telegram)

In its own words, on Official MCP Registry:

Telegram on your own account: read, search, send and press bot buttons. Writes need your approval.

How to run each

telegram-per-project As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install telegram-per-project@claude-community

Better-TG-CLI (Telegram) As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio better-tg-cli -- npx -y better-tg-cli mcp

Commands 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

Only telegram-per-project asks for

  • NODE_PATH

Only Better-TG-CLI (Telegram) asks for

  • TG_PROFILE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: telegram-per-project · What it can do: Better-TG-CLI (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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built