Heroku vs mtdt — Salesforce DevOps
Heroku is an MCP server published by heroku. Marketplaces we read that list it: 1 (Docker MCP Catalog). mtdt — Salesforce DevOps is an MCP server published by mtdt.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  mtdt — Salesforce DevOps |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:bc972fc22f00 Forks (GitHub): 30 Pulls (Docker Hub): 20 521 Stars (Docker Hub): 2 Stars (GitHub): 82 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.2 Forks (GitHub): 0 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
| Fact | Heroku | mtdt — Salesforce DevOps |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 82 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 20 521 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | On your machine (mcp/heroku) | Remote server (mcp.mtdt.io) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 34 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/heroku/heroku-mcp-server | github.com/mtdt-io/mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (28 h ago) |
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.
mtdt — Salesforce DevOps
mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)
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)
mtdt — Salesforce DevOps As a remote MCP server
claude mcp add --transport http mtdt https://mcp.mtdt.ioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only mtdt — Salesforce DevOps has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of mtdt — Salesforce DevOps publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of mtdt — Salesforce DevOps publish no settings it asks for, so we do not compare settings.
What it can do: Heroku · What it can do: mtdt — Salesforce DevOps · 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.