heroku

Official
Local
73
Signed
GitHub Repo

Overview

The heroku-mcp-server is a Model Context Protocol (MCP) server that enables AI assistants and agents to interact directly with the Heroku platform through a structured, AI-friendly interface. It allows AI-driven workflows to inspect applications, manage deployments, review configuration, and reason about runtime behavior without switching tools or manually using the Heroku CLI or dashboard.

This server is ideal for application operations, deployment automation, troubleshooting, and platform management workflows on Heroku.

Transport

stdio

Tools

  • list_apps
  • get_app_info
  • create_app
  • rename_app
  • transfer_app
  • deploy_to_heroku
  • deploy_one_off_dyno
  • ps_list
  • ps_scale
  • ps_restart
  • list_addons
  • get_addon_info
  • create_addon
  • maintenance_on
  • maintenance_off
  • get_app_logs
  • pipelines_create
  • pipelines_promote
  • pipelines_list
  • pipelines_info
  • list_teams
  • list_private_spaces
  • pg_psql
  • pg_info
  • pg_ps
  • pg_locks
  • pg_outliers
  • pg_credentials
  • pg_kill
  • pg_maintenance
  • pg_backups
  • pg_upgrade

Key Capabilities

  • Application lifecycle management — Create, rename, transfer, and inspect Heroku apps programmatically.
  • Deployment workflows — Support AI-driven deploys, promotions, and operational actions.
  • Runtime insight — Reason about dynos, process scaling, and application health.
  • Configuration and add-ons — Inspect and manage add-ons and environment-related context.
  • Operational visibility — Access logs and platform metadata for debugging and analysis.

How It Works

The heroku MCP server runs as an MCP service and connects to Heroku using an authenticated API token with appropriate scopes. AI clients communicate with the server over the MCP protocol to request application context or perform platform actions as part of larger reasoning workflows.

The server handles authentication, request execution, and response normalization when interacting with Heroku’s APIs, returning structured results that AI assistants can reason over directly. This abstraction removes the need for clients to manage Heroku-specific API details while ensuring all actions respect Heroku’s permission and access model.

By exposing Heroku’s platform surface through MCP, the server enables conversational and automated workflows such as application inspection, deployment analysis, and operational troubleshooting — all inside a single AI-driven environment.