Ext Ops Panel
Open dashboard
Comparison

Heroku vs tgcloud — Telegram serverless bots

Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). tgcloud — Telegram serverless bots is an MCP server published by sdamarketing. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceHerokutgcloud — Telegram serverless bots
Docker MCP Catalog Listed
Version: sha256:bc972fc22f00
Forks (GitHub): 30
Pulls (Docker Hub): 20 533
Stars (Docker Hub): 2
Stars (GitHub): 82
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.3
Downloads/month (npm): 738
Downloads/week (npm): 738
Forks (GitHub): 0
Stars (GitHub): 1
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

Heroku vs tgcloud — Telegram serverless bots
FactHerokutgcloud — Telegram serverless bots
Marketplaces that list it11
Stars (GitHub) (differs)82 (better)1 (worse)
Pulls (Docker Hub) (differs)20 533No figure on Docker Hub
Forks (GitHub) (differs)30 (better)0 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/heroku)On your machine (tgcloud-mcp)
Transportstdiostdio
Tools it declares (differs)34Not published
Environment variables it asks for (differs)1, secrets among them: 14, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/heroku/heroku-mcp-servergithub.com/sdamarketing/tgcloud_mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

Heroku

In its own words, on Docker MCP Catalog:

Heroku Platform MCP Server using the Heroku CLI.

tgcloud — Telegram serverless bots

In its own words, on Official MCP Registry:

MCP server for Telegram serverless bots: lifecycle, deploys, migrations, webhooks via tgcloud CLI

How to run each

Heroku As a local MCP server: Docker image

Claude Code
claude mcp add --env "HEROKU_API_KEY=<YOUR_HEROKU_API_KEY>" --transport stdio heroku -- docker run -i --rm -e HEROKU_API_KEY mcp/heroku

Requires: HEROKU_API_KEY (secret)

tgcloud — Telegram serverless bots As a local MCP server: npm package

Claude Code
claude mcp add --env "TGCLOUD_TOKEN=<YOUR_TGCLOUD_TOKEN>" --transport stdio tgcloud-mcp -- npx -y tgcloud-mcp

Requires: TGCLOUD_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of tgcloud — Telegram serverless bots publish no list of tools, so we do not compare tools.

Settings each asks for

Only Heroku asks for

  • HEROKU_API_KEY (secret)

Only tgcloud — Telegram serverless bots asks for

  • TGCLOUD_CLI
  • TGCLOUD_CLI_ARGS
  • TGCLOUD_TIMEOUT_MS
  • TGCLOUD_TOKEN (secret)

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

What it can do: Heroku · What it can do: tgcloud — Telegram serverless bots · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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