Heroku (PaaS) MCP Server

create_app

Provision a fresh structural App container on Heroku

delete_app

Traffic routing instantly yields persistent 404/no web-dynos responses. Highly destructive. Permanently wipe an active App from Heroku servers

get_app_info

g. heroku-22, heroku-24). Confirms exact application routing URL mapping, total slug (code) size in memory, and regional datacenter placements (US or EU) verifying global latency strategies. Fetch intricate runtime constraints and framework details of an App

list_addons

Retrieve third-party Platform Add-ons mapping to an App

list_apps

Use this to discover App IDs, web URL designations, and git repository targets required to execute operational commands downstream. List all standard applications actively hosted on Heroku PaaS

list_config_vars

Retrieves highly confidential database tokens `DATABASE_URL`, SendGrid passwords, or OAuth keys. Dump decrypted Application Environment Variables

list_dynos

1, worker.1). Tracks exactly whether the dyno is "up", "crashed", "idle", or "starting" based on the internal slug runner engine's telemetry. List discrete containerized Dynos executing inside an App

restart_all_dynos

Often resolves ephemeral memory-leaks in Node.js or Ruby runtimes stalling standard request processing. Hard reboot all containers tied to an entire Application

restart_specific_dyno

Exceedingly useful for unsticking hung asynchronous queue workers without impacting active web traffic on the primary frontend replicas. Selectively reboot one isolated Dyno instance (e.g. worker.2)

toggle_maintenance_mode

Crucial for orchestrating complex sequential database migrations without encountering corrupted states from active sessions. Rapidly switch an Application's Maintenance Mode switch