Heroku MCP Server

What It Does

Full Heroku app lifecycle management through MCP. Deploy apps, scale dynos, restart processes, tail logs, monitor performance, manage Postgres and Redis add-ons, run one-off dynos for sandboxed code execution, and manage deployment pipelines.

Two modes: local CLI integration (heroku mcp:start) that reuses your existing Heroku CLI authentication, or remote OAuth at https://mcp.heroku.com/mcp with no local install required.

What It Does Well

• CLI-native integration reuses existing auth seamlessly. If you already have the Heroku CLI installed and authenticated, heroku mcp:start starts the MCP server using your existing session. No separate API keys, no OAuth configuration, no tokens in config files. The simplest auth story of any PaaS MCP server.
• One-off dynos provide sandboxed code execution. Claude can spin up temporary dynos to run code, scripts, or commands in an isolated Heroku environment. This is useful for testing deployment scripts or running database migrations without affecting your local machine.
• Remote OAuth option means zero local dependencies. The hosted server at https://mcp.heroku.com/mcp handles authentication through the browser. No CLI install, no Node.js, no npx. Configure the URL and authenticate.

What It Doesn’t Do Well

• Requires Heroku CLI globally installed for local mode. The heroku mcp:start path needs the Heroku CLI at v10.8.1+. If you don’t already use Heroku’s CLI, that’s a global install just for MCP. The remote OAuth path avoids this.
• Early development status acknowledged by Heroku. The server notes it’s in early development. Features may change, and edge cases in app management may not be fully covered yet.

Setup Notes

For existing Heroku users: heroku mcp:start and you’re done. The CLI handles everything.

For new setups or users who prefer remote: configure https://mcp.heroku.com/mcp as an HTTP MCP server. OAuth handles auth through the browser.

The npx alternative (npx -y @heroku/mcp-server) requires HEROKU_API_KEY as an environment variable instead of using CLI session auth.

Works with Claude Desktop, Cursor, Windsurf, Zed, and Agentforce (Salesforce integration).

Config

CLI (recommended for existing Heroku users):

{
  "mcpServers": {
    "heroku": {
      "command": "heroku",
      "args": ["mcp:start"]
    }
  }
}

Remote (no local install):

{
  "mcpServers": {
    "heroku": {
      "url": "https://mcp.heroku.com/mcp"
    }
  }
}

npx (alternative local):

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

Tested With

• Claude Desktop on Windows 11

{
  "mcpServers": {
    "heroku-mcp": {
      "command": "heroku",
      "args": [
        "mcp:start"
      ]
    }
  }
}