Heroku MCP Server

What this server does

Heroku's official MCP server lets the assistant operate your apps through the Platform API: list apps, read config and add-ons, inspect and scale dynos, run one-off commands, and tail logs. During a deploy or an incident the model can check what is running, read the logs, and scale a process type without you switching to the CLI. The API token scopes what it can do, so a token from a least-privilege account keeps the surface bounded. Pair it with a logs question and the model can tell you why a release is unhealthy.

Tools included

• list_apps

  List your Heroku apps.

• get_app_info

  Read details and config for an app.

• list_dynos

  List the dynos running for an app.

• scale_dyno

  Scale a process type up or down.

• view_logs

  Stream recent app logs.

The authoritative list comes from the server's tools/list at runtime. This catalog entry may lag the upstream until the next ToolPiper release.

Install in ToolPiper

ToolPiper handles the JSON configuration. Click Install, fill in any required tokens, and the server is ready in your chat.

Install in another client

{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ]
    }
  }
}

Example prompts

Security notes

The API token can read and change your apps, including scaling dynos and reading config vars that often hold other services' secrets. Treat it as a high-value credential, scope it to a least-privilege account, and rotate it from the account dashboard if it leaks. Config vars returned by get_app_info may expose downstream credentials, so be careful what you echo into chat.

Related tools