MCP Heroku Server

You can manage Heroku apps and deployments through a focused MCP server that opens a streamlined interface to the Heroku Platform API. This server enables you to list apps, view deployment history, adjust dyno counts, access logs, manage environment variables, and handle add-ons from a single MCP client workflow, making it easier to operate AI-assisted workflows that rely on Heroku-backed resources.

How to use

To use this MCP server, add it to your MCP client configuration and start it with your Heroku API key. Your client can then call the available tools to list apps, view releases, restart or scale dynos, fetch logs, and manage configuration and add-ons for each app.

How to install

Prerequisites you need on your system before installing this MCP server:

• Node.js 16+ for running the MCP server
• Heroku CLI is optional but helpful for generating API keys
• A Heroku API Key from your dashboard account settings

Install and run using the following steps. Each command should be entered on its own line.

# Install the MCP server globally (example shown in recommended flow)
npm install -g @artik0din/mcp-heroku

# Set your Heroku API key in the environment
export HEROKU_API_KEY=your-heroku-api-key

# Start the MCP server
mcp-heroku

Configuration and usage notes

Configure your MCP client to use the MCP server. You can provide the server via an npx invocation so your client can directly load the server module.

# Claude Desktop configuration example
{
  "mcpServers": {
    "heroku": {
      "command": "npx",
      "args": ["@artik0din/mcp-heroku"],
      "env": {
        "HEROKU_API_KEY": "your-heroku-api-key-here"
      }
    }
  }
}

Security and environment

The server uses your Heroku API key for authentication and reads it from environment variables. No credentials are stored or cached by the server. All communications with Heroku occur over HTTPS.

Troubleshooting

If you encounter authentication errors, verify that your HEROKU_API_KEY is correct and has the necessary permissions in your Heroku account. Ensure that the environment variable is available to the MCP server process when it starts.

Examples of common tasks

List all apps, view the deployment history, and manage dynos for a specific app using the MCP tools exposed by this server.

# Example: Scale web dynos for an app named my-app to 2 dynos
# This assumes you are using an MCP client with the appropriate tool bindings
# The following is a representative usage pattern within an MCP client context

# Tools used (names reflect the MCP endpoints):
# heroku_list_apps, heroku_scale, heroku_get_logs

Available tools

heroku_list_apps

List all your Heroku apps. Optionally filter by team with the team parameter.

heroku_get_app

Get detailed information about a specific Heroku app by name.

heroku_list_releases

View the deployment history for an app, with an optional limit on the number of releases returned.

heroku_restart

Restart dynos for a specific app, with an optional dyno selector to target a single dyno.

heroku_scale

Scale dynos for an app by type and quantity, with an optional size parameter to adjust the dyno class.

heroku_get_logs

Retrieve application logs with options to specify lines, dyno, and source.

heroku_list_addons

List add-ons attached to a specific app to monitor databases, caches, and other services.

heroku_config_vars

Manage environment variables for a specific app, including setting new values and listing current ones.