Herokuvf.sr

Q: Does Heroku need an API key?

Yes. It reads HEROKU_API_KEY from its environment, and HEROKU_API_KEY is a secret. Put the value in your client's config on your own machine, never in a shared file.

listing.by · home.legend.verified

Deploy, scale and inspect Heroku apps, add-ons, Postgres databases and logs from your AI assistant.

state.local.longlisting.badge.runs_withstate.key.long

listing.install

listing.local.explain

npx -y @heroku/mcp-server

listing.local.needs listing.local.note

HEROKU_API_KEY listing.env.secret Heroku API key (heroku authorizations:create).

act.add_to

listing.about

Connects an AI assistant to the Heroku Platform through the Heroku CLI. It can list and inspect apps, create, rename and transfer them, and deploy projects with an app.json configuration. It works on Common Runtime, Cedar Private and Shield Spaces, and Fir Private Spaces.

Runs locally over stdio. The recommended launch command is heroku mcp:start (Heroku CLI 10.8.1 or later), which reuses your CLI login. Alternatively, run npx -y @heroku/mcp-server with the HEROKU_API_KEY environment variable set to a Heroku authorization token. The project describes itself as in early development.

listing.can

List Heroku apps filtered by personal, collaborator, team or space
Get app details including configuration, dynos and add-ons
Create, rename and transfer apps
Deploy projects to Heroku using app.json
Works with Common Runtime, Private Spaces and Shield Spaces

listing.tools

listing.notools.key

listing.prompts

List my Heroku apps that belong to the team
Show configuration and dynos for my app my-app
Create a new Heroku app in the eu region
Deploy this project to Heroku using its app.json

listing.setup.h

listing.setup.local

Claude Code

Run this in a terminal, in your project folder:

claude mcp add --transport stdio heroku --env "HEROKU_API_KEY=<YOUR_HEROKU_API_KEY>" -- npx -y @heroku/mcp-server

Start Claude Code and type /mcp. heroku should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:

claude_desktop_config.json

{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ],
      "env": {
        "HEROKU_API_KEY": "<YOUR_HEROKU_API_KEY>"
      }
    }
  }
}

Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json

{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ],
      "env": {
        "HEROKU_API_KEY": "<YOUR_HEROKU_API_KEY>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json

{
  "servers": {
    "heroku": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ],
      "env": {
        "HEROKU_API_KEY": "${input:heroku-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "heroku-api-key",
      "description": "HEROKU_API_KEY",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):

mcp_config.json

{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ],
      "env": {
        "HEROKU_API_KEY": "<YOUR_HEROKU_API_KEY>"
      }
    }
  }
}

Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add heroku --env "HEROKU_API_KEY=<YOUR_HEROKU_API_KEY>" -- npx -y @heroku/mcp-server

Or edit ~/.codex/config.toml directly:

config.toml

[mcp_servers.heroku]
command = "npx"
args = ["-y", "@heroku/mcp-server"]
env = { HEROKU_API_KEY = "<YOUR_HEROKU_API_KEY>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "HEROKU_API_KEY=<YOUR_HEROKU_API_KEY>" heroku npx -- -y @heroku/mcp-server

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ],
      "env": {
        "HEROKU_API_KEY": "<YOUR_HEROKU_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

listing.faq

Can I paste mcp.tc/i/heroku into my MCP client?

No. Heroku runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @heroku/mcp-server.

Does Heroku need an API key?

Yes. It reads HEROKU_API_KEY from its environment, and HEROKU_API_KEY is a secret. Put the value in your client's config on your own machine, never in a shared file.

Is Heroku a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @heroku/mcp-server, which needs Node.js.

What can Heroku do?

You can list Heroku apps filtered by personal, collaborator, team or space, get app details including configuration, dynos and add-ons and create, rename and transfer apps.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Heroku's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

Markdown

[![Heroku on mcp.tc](https://mcp.tc/i/heroku/badge.svg)](https://mcp.tc/i/heroku)

HTML

<a href="https://mcp.tc/i/heroku"><img src="https://mcp.tc/i/heroku/badge.svg" alt="Heroku on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML

<script src="https://mcp.tc/w/heroku.js" async></script>

listing.em.widget_note

iframe

HTML

<iframe src="https://mcp.tc/embed/heroku" title="Heroku on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note