Heroku vs io.github.floomhq/floom
Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.floomhq/floom is an MCP server published by floomhq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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 |  Heroku |  io.github.floomhq/floom |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:bc972fc22f00 Forks (GitHub): 30 Pulls (Docker Hub): 20 428 Stars (Docker Hub): 2 Stars (GitHub): 82 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.6 Downloads/month (npm): 131 Downloads/week (npm): 19 Forks (GitHub): 3 Stars (GitHub): 46 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 | Heroku | io.github.floomhq/floom |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 82 (better) | 46 (worse) |
| Pulls (Docker Hub) (differs) | 20 428 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 (better) | 3 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/heroku) | On your machine (@floomhq/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 34 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/heroku/heroku-mcp-server | github.com/floomhq/floom |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
Heroku
Heroku Platform MCP Server using the Heroku CLI.
io.github.floomhq/floom
Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.
How to run each
Heroku As a local MCP server: Docker image
claude mcp add --env "HEROKU_API_KEY=<YOUR_HEROKU_API_KEY>" --transport stdio heroku -- docker run -i --rm -e HEROKU_API_KEY mcp/herokuRequires: HEROKU_API_KEY (secret)
io.github.floomhq/floom As a local MCP server: npm package
claude mcp add --env "FLOOM_API_KEY=<YOUR_FLOOM_API_KEY>" --env "FLOOM_BASE_URL=<YOUR_FLOOM_BASE_URL>" --transport stdio floom -- npx -y @floomhq/mcp-serverRequires: FLOOM_API_KEY (secret), FLOOM_BASE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.floomhq/floom publish no list of tools, so we do not compare tools.
Settings each asks for
Only Heroku asks for
HEROKU_API_KEY (secret)
Only io.github.floomhq/floom asks for
FLOOM_API_KEY (secret)FLOOM_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Heroku · What it can do: io.github.floomhq/floom · 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.