Ext Ops Panel
Open dashboard
Comparison

Heroku vs cm64

Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). cm64 is a plugin bundle for AI coding tools published by cm64-studio. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceHerokucm64
Docker MCP Catalog Listed
Version: sha256:bc972fc22f00
Forks (GitHub): 30
Pulls (Docker Hub): 20 411
Stars (Docker Hub): 2
Stars (GitHub): 82
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
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 cm64
FactHerokucm64
Marketplaces that list it11
Stars (GitHub) (differs)82 (better)1 (worse)
Pulls (Docker Hub) (differs)20 411No figure on Docker Hub
Forks (GitHub) (differs)30 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/heroku)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)34Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/heroku/heroku-mcp-servergithub.com/cm64-studio/cm64-cli
Changes in the last 7 days00
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.

cm64

In its own words, on Claude Code: claude-plugins-community:

Build and deploy web apps in 60 seconds. CM64 is a full PaaS with a git-like CLI — pull projects locally, edit components/pages/functions with Claude Code, push changes, and deploy to production. Zero config, instant hosting, built for AI-first development.

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)

cm64 As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install cm64@claude-community

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

Tools each declares

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

Settings each asks for

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

What it can do: Heroku · What it can do: cm64 · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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