WireCat Telegram vs Telegram AI CLI MCP
WireCat Telegram is an MCP server published by wirecat.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Telegram AI CLI MCP is an MCP server published by stufently. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |  WireCat Telegram |  Telegram AI CLI MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.106.0 Forks (GitHub): 3 Stars (GitHub): 12 Not marked · First seen |
Listed Version: 0.1.3 Downloads/month (PyPI): 0 Downloads/week (PyPI): 195 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.1.3 Downloads/month (PyPI): 0 Downloads/week (PyPI): 195 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 | WireCat Telegram | Telegram AI CLI MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 12 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | 2026-10-29 (better) | 2026-10-15 (worse) |
| Where it runs (differs) | On your machine (@wirecat/tg-cli) | On your machine (telegram-ai-cli-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/wirecatlabs/tg-cli | github.com/stufently/telegram-ai-cli-mcp |
| Changes in the last 7 days (differs) | 15 | 0 |
| First seen (differs) | 2026-10-27 | 2026-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
WireCat Telegram
Your Telegram account for agents: read, search and send messages. Sign in with the tg CLI first.
Telegram AI CLI MCP
Read a personal Telegram account over MTProto; every write is a plan a human applies.
How to run each
WireCat Telegram As a local MCP server: npm package
claude mcp add --transport stdio tg-cli -- npx -y @wirecat/tg-cli mcp serve --profiles allTelegram AI CLI MCP As a local MCP server: PyPI package
claude mcp add --transport stdio telegram-ai-cli-mcp -- uvx telegram-ai-cli-mcp mcpCommands 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 WireCat Telegram publish no settings it asks for, so we do not compare settings.
What it can do: WireCat Telegram · What it can do: Telegram AI CLI MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.