Ext Ops Panel
Open dashboard
Comparison

tg-agent vs Telegram Bot MCP Server

tg-agent is a plugin bundle for AI coding tools published by axisrow. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Telegram Bot MCP Server is an MCP server published by cyuanxv. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacetg-agentTelegram Bot MCP Server
Community marketplace axisrow/tg_content_factory Listed
Version: 0.2.4.2
Forks (GitHub): 8
Stars (GitHub): 36
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
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

tg-agent vs Telegram Bot MCP Server
Facttg-agentTelegram Bot MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)36 (better)0 (worse)
Forks (GitHub) (differs)8 (better)0 (worse)
Last release (differs)2026-10-24 (better)2026-10-24 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (@cyuanxv/telegram-bot-mcp-server)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 3
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/axisrow/tg_content_factorygithub.com/cyuanxv/telegram-bot-mcp-server
Changes in the last 7 days (differs)13
First seen (differs)2026-10-142026-10-22

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

tg-agent

In its own words, on Community GitHub marketplaces:

Full-spectrum Telegram access for coding agents through the tg-agent CLI: channels, chats, messages, media, admin, content pipelines, analytics.

Telegram Bot MCP Server

In its own words, on Official MCP Registry:

Self-hosted Telegram Bot MCP server for rich text, media and interactive buttons.

How to run each

tg-agent As a Claude Code plugin

Claude Code
/plugin marketplace add axisrow/tg_content_factory
/plugin install tg-agent@tg-agent-marketplace

Telegram Bot MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: MCP_API_KEY (secret), TELEGRAM_BOT_TOKEN (secret), TELEGRAM_CHAT_ID (secret)

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

The marketplaces of tg-agent publish no settings it asks for, so we do not compare settings.

What it can do: tg-agent · What it can do: Telegram Bot MCP Server · 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.

Where the data comes from: how the catalog is built