Heroku

Heroku

Official

Manage Heroku apps, dynos, add-ons, and Postgres from an AI agent.

Score 76(?)HerokuApache-2.081Verified Top MCPs for Web Hosting →

Quick answer

What it does

Surfaces Heroku Platform operations — apps, dynos, add-ons, pipelines, Postgres — as MCP tools.

Best for

  • App lifecycle (create, rename, transfer)
  • Dyno scaling and restart
  • Add-on management
  • Heroku Postgres ops (info, locks, backups, upgrade)

Not for

  • Unattended production scaling
  • Add-on provisioning without cost awareness

Source: top-mcps.com/mcp/heroku — verified Aug 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "heroku": {
          "command": "heroku",
          "args": [
            "mcp:start"
          ],
          "env": {
            "HEROKU_API_KEY": "${HEROKU_API_KEY}"
          }
        }
      }
    }

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export HEROKU_API_KEY=your_heroku_token
    claude mcp add heroku -- heroku mcp:start

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
      "mcpServers": {
        "heroku": {
          "command": "heroku",
          "args": [
            "mcp:start"
          ],
          "env": {
            "HEROKU_API_KEY": "${HEROKU_API_KEY}"
          }
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
      "servers": {
        "heroku": {
          "command": "heroku",
          "args": [
            "mcp:start"
          ],
          "env": {
            "HEROKU_API_KEY": "${HEROKU_API_KEY}"
          }
        }
      }
    }

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "heroku": {
          "command": "heroku",
          "args": [
            "mcp:start"
          ],
          "env": {
            "HEROKU_API_KEY": "${HEROKU_API_KEY}"
          }
        }
      }
    }

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "heroku": {
          "command": "heroku",
          "args": [
            "mcp:start"
          ],
          "env": {
            "HEROKU_API_KEY": "${HEROKU_API_KEY}"
          }
        }
      }
    }

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "stdio",
              "command": "heroku",
              "args": [
                "mcp:start"
              ],
              "env": {
                "HEROKU_API_KEY": "${HEROKU_API_KEY}"
              }
            }
          }
        ]
      }
    }

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
    [mcp_servers.heroku]
    command = "heroku"
    args = [
      "mcp:start",
    ]
    env = { HEROKU_API_KEY = "${HEROKU_API_KEY}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "heroku": {
          "command": {
            "path": "heroku",
            "args": [
              "mcp:start"
            ]
          },
          "env": {
            "HEROKU_API_KEY": "${HEROKU_API_KEY}"
          }
        }
      }
    }

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Heroku doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set HEROKU_API_KEY in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. web hosting work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-hosting
Compare Heroku against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Heroku MCP vs [Railway MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/heroku
- top-mcps.com listing for Railway
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Heroku MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/heroku (fetch https://top-mcps.com/mcp/heroku.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (HEROKU_API_KEY) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Web Hosting MCPs

Other tools in the same category worth evaluating.

Cloudflare
Official

Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.

cloudflare, edge, workers, dns
5 minMedium
Official

Deploy a site, read the build, and manage projects, forms and extensions with Netlify's official MCP server.

netlify, web-hosting, deployment, jamstack
5 minLow
Render
Official

Provision Render services, read deploy logs and metrics, and query Postgres read-only — over a hosted OAuth MCP.

render, web-hosting, deployment, paas
5 minMedium

Compared with Heroku

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Web Hosting? See all Web Hosting MCPs →