Ext Ops Panel
Open dashboard
Comparison

Heroku vs Vercel MCP Pro

Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). Vercel MCP Pro is an MCP server published by helbertparanhos. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceHerokuVercel MCP Pro
Docker MCP Catalog Listed
Version: sha256:bc972fc22f00
Forks (GitHub): 30
Pulls (Docker Hub): 20 752
Stars (Docker Hub): 2
Stars (GitHub): 82
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 498
Downloads/week (npm): 35
Forks (GitHub): 1
Stars (GitHub): 0
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 Vercel MCP Pro
FactHerokuVercel MCP Pro
Marketplaces that list it11
Stars (GitHub) (differs)82 (better)0 (worse)
Pulls (Docker Hub) (differs)20 752No figure on Docker Hub
Forks (GitHub) (differs)30 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/heroku)On your machine (vercel-mcp-pro)
Transportstdiostdio
Tools it declares (differs)34Not published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/heroku/heroku-mcp-servergithub.com/helbertparanhos/vercel-mcp-pro
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.

Vercel MCP Pro

In its own words, on Official MCP Registry:

Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API

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)

Vercel MCP Pro As a local MCP server: npm package

Claude Code
claude mcp add --env "VERCEL_TOKEN=<YOUR_VERCEL_TOKEN>" --transport stdio vercel-mcp-pro -- npx -y vercel-mcp-pro

Requires: VERCEL_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 Vercel MCP Pro publish no list of tools, so we do not compare tools.

Settings each asks for

Only Heroku asks for

  • HEROKU_API_KEY (secret)

Only Vercel MCP Pro asks for

  • VERCEL_READONLY
  • VERCEL_TEAM_ID
  • VERCEL_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: Vercel MCP Pro · 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