PLATFORM AS A SERVICE / Heroku
Heroku Platform MCP Server
Lets an assistant read, manage and operate Heroku apps, add-ons and pipelines, authenticating through the installed Heroku CLI or an API key.
“This server provides a robust set of tools and capabilities that enable LLMs to read, manage, and operate Heroku Platform resources.”
01 / THE REASONING
Why this made the selection.
- Publisher-maintained PaaS surface: apps, add-ons and pipelines are operable without hand-rolling Heroku API calls.
- CLI-context authentication avoids pasting an API key into client configuration when the Heroku CLI path is used.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md: CLI prerequisite, heroku mcp:start path, API-key path and per-client stdio configurations.
- package.json: @heroku/mcp-server identity, bin/heroku-mcp-server.mjs entrypoint and MCP SDK dependency.
- LICENSE.txt: Apache-2.0 terms for the repository source.
- README.md Available Tools and Environment Variables sections at the same commit
Our findings
- All documented configurations are stdio command invocations; no remote or HTTP transport is documented.
- The CLI path reuses existing Heroku CLI authentication so no key enters the client configuration.
- Corrected 2026-10-13: the previous configExample (command heroku with args mcp:start) matched no README block. It is now the README Claude Desktop block, whose command is the single string heroku mcp:start. The VS Code and Zed blocks split it into command and args.
- Available Tools lists 32 tools in seven groups. The ones that change or run things are create_app, rename_app, transfer_app, deploy_to_heroku, deploy_one_off_dyno, ps_scale, ps_restart, create_addon, maintenance_on, maintenance_off, pipelines_create, pipelines_promote, pg_psql, pg_credentials, pg_kill, pg_backups and pg_upgrade.
- package.json names the package @heroku/mcp-server at this commit and at HEAD 4afcbe1a042b78e81385280ac5adaeb0000dba6e (2026-10-13).
Not established by this review
- Server startup, authentication and tool execution were not tested.
- No changing or executing tool (deploy_one_off_dyno, pg_psql, transfer_app) was called.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Install Heroku CLI 10.8.1+ and log in, then add the documented heroku mcp:start stdio configuration.
- Without the CLI, configure the packaged server with a Heroku API key kept outside shared configuration.
Before you start
- Heroku CLI 10.8.1+ with an authenticated account, or a Heroku API key.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"heroku": {
"command": "heroku mcp:start"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Heroku MCP server readme ↗Checked
https://github.com/heroku/heroku-mcp-server/blob/5a070deeacc5eb1481884080e513f3be5528046f/README.md
Supports: summary, install, compatibility, access, transports, configExample, whySelected, bestFor, limitations, upstreamDescription, Tool list and changing tools, deploy_one_off_dyno and pg_psql execution
- Repository licence ↗Checked
https://github.com/heroku/heroku-mcp-server/blob/5a070deeacc5eb1481884080e513f3be5528046f/LICENSE.txt
Supports: license
- Package manifest ↗Checked
https://github.com/heroku/heroku-mcp-server/blob/5a070deeacc5eb1481884080e513f3be5528046f/package.json
Supports: Package name @heroku/mcp-server