herokulisted

# /heroku — Heroku through MCP Everything goes through the **`heroku` MCP server**, which ships inside the Heroku CLI (`heroku mcp:start`). This skill issues no REST calls to `api.heroku.com` and has no curl fallback. Wiring, the scoped-token setup and permission tiers: [docs/mcp-servers.md](../../docs/mcp-servers.md). ## First, check the server is there Tools appear as `mcp__heroku__<tool>`. If none are available, say so and stop. Do not fall back to `curl api.heroku.com` or to the `heroku` CLI through Bash — both are what the guard hooks refuse. Check with `claude mcp list`. ## When to Use - Is the app up: dyno state, recent logs, release history - Add-on inventory, plans, and what a given add-on is - Postgres health: connections, locks, slow queries, backups, maintenance - Pipeline layout, and which app sits in which stage ## When NOT to Use - Deploying → `git push heroku main`, or your CI - Buildpack or Procfile problems → those are repo-side - Ad-hoc SQL → the `postgres` skill with a `read_only = true` profile - Anything needing Dashboard 2FA ## Tool map Read: | You want | Tool | |---|---| | apps | `list_apps`, `get_app_info` | | logs | `get_app_logs` | | dynos | `ps_list` | | add-ons | `list_addons`, `get_addon_info`, `list_addon_services`, `list_addon_plans` | | pipelines | `pipelines_list`, `pipelines_info` | | teams, spaces | `list_teams`, `list_private_spaces` | | Postgres health | `pg_info`, `pg_ps`, `pg_locks`, `pg_outliers`, `pg_backups`, `pg_maintenan