Log inSubmit server
Heroku MCP Server logo

Heroku MCP Server

Manage Heroku apps, dynos, add-ons, pipelines, logs, and PostgreSQL operations through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Heroku MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "heroku-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@heroku/mcp-server"
      ],
      "env": {
        "HEROKU_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Heroku MCP Server MCP server connects AI agents to Heroku Platform resources through the Heroku CLI or a Heroku authorization token. It covers app lifecycle operations, deployments, dyno scaling and restarts, add-ons, pipelines, logs, and PostgreSQL administration. Use it when an agent needs to inspect or change Heroku environments, run one-off dynos, or operate Heroku Postgres. It supports Common Runtime, Cedar Private and Shield Spaces, and Fir Private Spaces.

Use cases

  • Inspect Heroku apps and their runtime resources
  • Deploy projects and promote applications through pipelines
  • Scale, resize, or restart Heroku dynos
  • Run SQL and investigate PostgreSQL queries or locks

Key features

  • Heroku app creation, transfer, renaming, and deployment
  • Dyno listing, scaling, resizing, and restart operations
  • Add-on provisioning and inspection
  • Pipeline creation, inspection, and promotion
  • Heroku Postgres SQL and process administration
  • CLI-session or API-key authentication

Tools32

What Heroku MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~459 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 1h ago via OSV.dev · @heroku/mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars82Stargazers on the source repository.
npm downloads34kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed32Callable tools this server registers over MCP.

How Heroku MCP Server works

What Heroku MCP Server does

Heroku MCP Server exposes Heroku Platform operations as Model Context Protocol tools. Agents can inspect applications and their configuration, create or rename apps, transfer ownership, deploy projects, and run temporary commands on one-off dynos. Application operations can be filtered or scoped by personal ownership, collaborators, teams, regions, and spaces where the relevant tool supports those settings.

The server also covers day-to-day runtime management. It can list dynos, change dyno counts or sizes, restart individual dynos or process types, toggle maintenance mode, and retrieve application logs. Add-on tools list services across apps, inspect a specific add-on, and provision a new one.

Pipeline and database operations are included as well. Agents can create, inspect, list, and promote pipelines. Heroku Postgres tools execute SQL, show database details, inspect active queries and locks, identify expensive queries, manage credentials, terminate database processes, and display maintenance information.

How it works

The server runs as a local MCP process and exposes Heroku operations to compatible clients. The recommended launch path is heroku mcp:start, which uses the authentication already established in the local Heroku CLI session. This avoids putting an API token in the MCP client configuration.

An alternative launch path uses npx -y @heroku/mcp-server. That mode authenticates with the HEROKU_API_KEY environment variable, which should contain a Heroku authorization token. The token can be created with the Heroku CLI or through Heroku account settings.

Setup and configuration

Install the Heroku CLI globally before running the server; the documented minimum is version 10.8.1. Check the installed version with heroku --version.

For CLI-based authentication, configure the client to run:

sh
heroku mcp:start

For token-based authentication, configure the client to run npx -y @heroku/mcp-server and provide HEROKU_API_KEY in the server environment. The repository includes configurations for Claude Desktop, Zed, Cursor, Windsurf, Cline, and VS Code. A Heroku deployment option is also available from the project repository.

Tools and capabilities

The tools are grouped around these operational areas:

  • App management: list, inspect, create, rename, transfer, and deploy applications.
  • Temporary execution: run commands or code in a sandboxed one-off dyno, with file creation, network access, environment variables, and automatic cleanup.
  • Dynos: list, scale, resize, and restart processes.
  • Add-ons: list, inspect, and provision add-ons.
  • Operations: enable or disable maintenance mode and retrieve logs.
  • Pipelines: create, list, inspect, and promote pipeline applications.
  • PostgreSQL: run SQL and inspect queries, locks, outliers, credentials, processes, and maintenance state.

Limitations and notes

The available tool set is in early development and may change as the project evolves. Access depends on the Heroku identity used by the CLI session or API token. The CLI requirement applies to the documented setup, including the heroku mcp:start command and the minimum supported CLI version. Deployments can use app.json configuration and support team deployments, private spaces, and environment setups.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Heroku MCP Server

Heroku MCP Server is an MCP server that connects AI agents to the Heroku Platform through the Heroku CLI or an API key. Its main tools list and manage apps, dynos, add-ons, pipelines, logs, and PostgreSQL databases, including deployment, scaling, maintenance, SQL queries, and database process operations.

Install the Heroku CLI globally at version 10.8.1 or higher, then configure your MCP client to run `heroku mcp:start`. You can alternatively launch `npx -y @heroku/mcp-server` and set `HEROKU_API_KEY` to a Heroku authorization token.

Yes, Heroku MCP Server works with Cursor. Configure Cursor to launch `heroku mcp:start` using your CLI login, or launch `npx -y @heroku/mcp-server` with `HEROKU_API_KEY` set to a Heroku authorization token.

Yes, it provides Heroku Postgres tools for executing SQL, viewing database information, inspecting active queries and locks, finding resource-intensive queries, managing credentials, terminating database processes, and viewing maintenance information.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHeroku MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/heroku-mcp-server?style=directory)](https://allmcps.com/mcp/heroku-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/heroku-mcp-server"><img src="https://allmcps.com/api/badge/heroku-mcp-server?style=directory" alt="Heroku MCP Server on AllMCPs" /></a>