Ext Ops Panel
Open dashboard
Comparison

Heroku vs Squish

Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). Squish is an MCP server published by squish.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceHerokuSquish
Docker MCP Catalog Listed
Version: sha256:bc972fc22f00
Forks (GitHub): 30
Pulls (Docker Hub): 21 157
Stars (Docker Hub): 2
Stars (GitHub): 82
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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 Squish
FactHerokuSquish
Marketplaces that list it11
Stars (GitHub) (differs)82No figure on GitHub
Pulls (Docker Hub) (differs)21 157No figure on Docker Hub
Forks (GitHub) (differs)30No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/heroku)Remote server (api.squish.co/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)34Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/heroku/heroku-mcp-serverNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-28
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 h ago, requires authentication

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.

Squish

In its own words, on Official MCP Registry:

Manage your Squish domains, DNS, hosting, backups and site files from your AI assistant.

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)

Squish As a remote MCP server

Claude Code
claude mcp add --transport http squish https://api.squish.co/mcp

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

Only Squish has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Squish publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Heroku · What it can do: Squish · 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