Ext Ops Panel
Open dashboard
Comparison

Heroku vs environment-manager

Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). environment-manager is a plugin bundle for AI coding tools published by GLINCKER Team. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
MarketplaceHerokuenvironment-manager
Docker MCP Catalog Listed
Version: sha256:bc972fc22f00
Forks (GitHub): 30
Pulls (Docker Hub): 20 546
Stars (Docker Hub): 2
Stars (GitHub): 82
Not marked · First seen
Not listed
Community marketplace glincker/claude-code-marketplace Not listed Listed
Version: 1.0.0
Forks (GitHub): 4
Stars (GitHub): 37
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 environment-manager
FactHerokuenvironment-manager
Marketplaces that list it11
Stars (GitHub) (differs)82 (better)37 (worse)
Pulls (Docker Hub) (differs)20 546No figure on Docker Hub
Forks (GitHub) (differs)30 (better)4 (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
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/heroku/heroku-mcp-servergithub.com/glincker/claude-code-marketplace
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-19

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.

environment-manager

In its own words, on Community GitHub marketplaces:

Manage development environments, configurations, and secrets across local, staging, and production

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)

environment-manager As a Claude Code plugin

Claude Code
/plugin marketplace add glincker/claude-code-marketplace
/plugin install environment-manager@glincker-marketplace

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

Tools each declares

The marketplaces of environment-manager publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Heroku · What it can do: environment-manager · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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