heroku

The Heroku MCP Server provides a specialized interface for model-context interactions with the Heroku Platform. It exposes a suite of tools that let an LLM read, manage, and operate on Heroku resources via the MCP protocol. The server authenticates using your Heroku CLI session by default when launched with the recommended commands, so you don’t need to manually manage API keys in every client. Core capabilities include listing apps, retrieving detailed app information, creating and renaming apps, transferring ownership, and deploying projects to Heroku. The server is designed to work with a variety of MCP clients (Claude Desktop, Zed, Cursor, Windsurf, VSCode, Trae, etc.) through standardized configurations, enabling seamless integration into your workflows.

Prerequisites:

• Node.js and npm (or npx available via npm) installed on your system.
• Heroku CLI installed and authenticated (recommended) if you plan to use the - start workflow via Heroku CLI. Ensure it’s v10.8.1+ as noted in the docs.

Option A: Run with npx (recommended for quick start)

1. Ensure you have an active Heroku CLI session or a valid HEROKU_API_KEY if you choose to supply one.
2. Install and run the MCP server via npx:

npx -y @heroku/mcp-server

3. If prompted, provide authentication details or export HEROKU_API_KEY in your environment:

export HEROKU_API_KEY=<your_token>

Option B: Use a dedicated MCP config for clients

1. Create a configuration file (e.g., mcp_config.json) with the following minimal setup:

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

2. Run the MCP server through your client using the provided configuration, ensuring the environment variable HEROKU_API_KEY is set if you are not using an active Heroku CLI session.

Notes and tips:

• If you use the npx method, you must provide a valid HEROKU_API_KEY when not relying on an authenticated Heroku CLI session.
• The server relies on the Heroku CLI for authentication in many configurations; ensure your CLI is installed and you’re logged in when using mcp:start interactions.
• Client support: Claude Desktop, Zed, Cursor, Windsurf, Cline, VSCode, Trae, and others can be configured to connect to this MCP server using the JSON snippets provided in the README.
• When using mcp-server via Heroku CLI, you can leverage existing CLI authentication context to avoid exposing API keys in configuration files.