Menu

AI

Heroku MCP Server: Tools, Setup and Security

What the Heroku Platform MCP Server lets AI agents do with apps, dynos, add-ons and Postgres, how to start it with the Heroku CLI, and which tools need care.

By: Irina ShvayaOctober 28, 2026

Heroku MCP Server: Tools, Setup and Security

This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.

The Heroku Platform MCP Server lets an AI agent read, manage and operate Heroku resources: apps, dynos, add-ons, pipelines and Heroku Postgres. Heroku publishes it as an open-source project that runs locally through the Heroku CLI.

Checked against: Heroku Dev Center: Heroku MCP Server on 28 October 2026. eSEOspace did not install or test this server.

Key Takeaways

  • The server runs locally. Heroku's recommended start command is heroku mcp:start, which needs Heroku CLI 10.8.1 or later.
  • heroku mcp:start reuses your CLI login, so you do not store an API key in a config file.
  • It documents 32 tools across apps, dynos, add-ons, logs, pipelines, teams and Postgres.
  • Heroku says the server "is currently in early development" and its tools may change.
  • Several tools can scale, transfer, kill or upgrade production resources. Keep approvals on.

At a glance

ItemDetail
PublisherHeroku
Official?Yes
HostingLocal (Heroku CLI or @heroku/mcp-server npm package)
Transportstdio
Sign-inHeroku CLI session, or a HEROKU_API_KEY token
Read or writeBoth
PriceNo separate MCP price listed
Source codeheroku/heroku-mcp-server on GitHub
Status"Early development" per Heroku

The Heroku MCP Server README says the server works on Common Runtime, Cedar Private and Shield Spaces, and Fir Private Spaces. The Dev Center article we checked was last updated on 24 July 2025, so confirm details in the repository too.

What it can do

The README lists these tools:

Application management: list_apps, get_app_info, create_app, rename_app, transfer_app, deploy_to_heroku, deploy_one_off_dyno.

Process and dyno management: ps_list, ps_scale, ps_restart.

Add-ons: list_addons, get_addon_info, create_addon.

Maintenance and logs: maintenance_on, maintenance_off, get_app_logs.

Pipelines: pipelines_create, pipelines_promote, pipelines_list, pipelines_info.

Teams and spaces: list_teams, list_private_spaces.

PostgreSQL: pg_psql, pg_info, pg_ps, pg_locks, pg_outliers, pg_credentials, pg_kill, pg_maintenance, pg_backups, pg_upgrade.

Two tools stand out. deploy_one_off_dyno runs code or commands "in a sandboxed environment on a Heroku one-off dyno." pg_psql executes SQL against your Heroku Postgres database.

How to connect it

Install the Heroku CLI at version 10.8.1 or higher. Then add the server to your client.

Recommended: heroku mcp:start. The README's config for Claude Desktop, Cursor, Windsurf (now Devin Desktop), Cline and Trae:

{
  "mcpServers": {
    "heroku": {
      "command": "heroku mcp:start"
    }
  }
}

For VS Code, the README uses:

{
  "mcp": {
    "servers": {
      "heroku": {
        "type": "stdio",
        "command": "heroku",
        "args": ["mcp:start"]
      }
    }
  }
}

Alternative: npm with an API key. Run npx -y @heroku/mcp-server and set HEROKU_API_KEY to a Heroku authorization token. You can create one with heroku authorizations:create or view the current one with heroku auth:token.

An optional MCP_SERVER_REQUEST_TIMEOUT variable sets command timeouts. The default is 15 seconds.

Security notes

  • Prefer the CLI session. Heroku lists "No need to manage or expose your Heroku API key" as a benefit of heroku mcp:start.
  • No built-in read-only mode is documented. The Dev Center page makes no statement about approvals or safeguards for destructive actions.
  • High-impact tools. transfer_app moves app ownership. ps_scale changes dyno counts and size, which affects cost. pg_kill terminates database processes. pg_upgrade upgrades Postgres. pg_credentials manages database credentials.
  • Arbitrary SQL. pg_psql runs any query the database user allows. Point the agent at a staging app first.
  • Token storage. If you must use HEROKU_API_KEY, keep it out of committed config files. See secret leakage in MCP.

Because nothing in the server limits writes, your MCP client's approval prompts are the main brake. Read tool annotations and the MCP security hub before you connect a production team.

Alternatives

Next step

Run the server against a non-production Heroku team first and watch which tools the agent reaches for. If you need custom guardrails, such as a read-only wrapper, our MCP development team can build one. More options are in the server directory.

Frequently asked questions

Is there a hosted Heroku MCP Server URL?

Not on the pages we checked. The Dev Center article covers only the local stdio server that runs through the Heroku CLI. The README does offer a Deploy to Heroku button for the project.

Does the Heroku MCP Server need an API key?

Not if you use heroku mcp:start, which reuses your CLI login. The npx method requires HEROKU_API_KEY.

Can the Heroku MCP Server run SQL on my database?

Yes. The pg_psql tool executes SQL queries against Heroku Postgres. Limit the database user's rights or test on staging first.

Is the Heroku MCP Server production-ready?

Heroku describes it as "currently in early development" and says available tools may evolve. Treat it accordingly and pin versions where you can.

You Might Also like to Read

Get a FREE Website Audit

Enter your website and get a 20–30 page SEO, GEO, AEO & CRO audit within 24 hours. Completely free.

Don't have a site yet? Get in touch →

Ready to speak with a marketing expert?
Give us a call! (916) 866-7893

Websites Launched
1407
Websites Launched
Marketing Experts
29
Marketing Experts
Hours of Dedicated Work
204533
Hours of Dedicated Work
Irina S.Benjamin G.Jeanette M.David G.