1.2.11 → 1.2.12
patch release, 12 October 2026No tool definition changed.
MCP servers / @heroku/mcp-server
@heroku/mcp-server
No tool definition changed across the 2 releases that started, up to 1.2.12.
npm package · npm page · recorded on 24 October 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. Method and limits.
Release by release
Releases tried: 1.2.7 (2026-09-03), did not start; 1.2.8 (2026-09-22), did not start; 1.2.9 (2026-09-24), did not start; 1.2.10 (2026-10-01), did not start; 1.2.11 (2026-10-06); 1.2.12 (2026-10-12).
Tools in 1.2.12
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition.
| Tool | Description | Pin |
|---|---|---|
| list_apps | List Heroku apps: owned, collaborator access, team/space filtering | d9847a5571f1 |
| get_app_info | Get app details: config, dynos, addons, access, domains | f93ab9da1975 |
| create_app | Create app: custom name, region (US/EU), team, private space | 1900773e10ba |
| rename_app | Rename app: validate and update app name | d59454473f0c |
| maintenance_on | Enable maintenance mode and redirect traffic for a Heroku app | 1c0e9faa8cbb |
| maintenance_off | Disable maintenance mode and restore normal app operations | 311f5d8a3e78 |
| get_app_logs | App logs: monitor/debug/filter by dyno/process/source | 14e28da62ec6 |
| list_private_spaces | Lists Heroku Private Spaces with CIDR blocks, regions, compliance and capacity details. JSON output supported. | 05c8023ea396 |
| list_teams | Lists accessible Heroku Teams. Use for: viewing teams, checking membership, getting team metadata, and verifying access. JSON output available. | ed11807eb6fe |
| list_addons | List add-ons: all apps or specific app, detailed metadata | da766f048fc3 |
| get_addon_info | Get add-on details: plan, state, billing | 11490233820e |
| create_addon | Create add-on: specify service, plan, custom names | 8ec092a1fccf |
| list_addon_services | List available add-on services and features | 1c15075fd7e4 |
| list_addon_plans | List service plans: features, pricing, availability | de859e5b115c |
| pg_psql | Execute SQL queries: analyze, debug, modify schema, manage data | d2e1da5eebd9 |
| pg_info | View database status: config, metrics, resources, health | e78ef12a727e |
| pg_ps | Monitor active queries: progress, resources, performance | 173af2329f8f |
| pg_locks | Analyze locks: blocked queries, deadlocks, concurrency | bf9f05335981 |
| pg_outliers | Find resource-heavy queries: performance, patterns, optimization | 67e7f540c30d |
| pg_credentials | Manage access: credentials, permissions, security, monitoring | dd2d252e2229 |
| pg_kill | Stop processes: stuck queries, blocking transactions, runaway operations | 813b0b3380bf |
| pg_maintenance | Track maintenance: windows, schedules, progress, planning | 3c790d82e556 |
| pg_backups | Manage backups: schedules, status, verification, recovery | 1fcf34026363 |
| pg_upgrade | Upgrade PostgreSQL: version migration, compatibility, safety | fe19bf769291 |
| ps_list | List and monitor Heroku app dynos. View running dynos, check status/health, monitor process states, verify configurations. | 952fa201b8af |
| ps_scale | Scale Heroku app dynos. Adjust quantities, change sizes, view formation details, manage resources. | 46c23850ac79 |
| ps_restart | Restart Heroku app processes. Restart specific dynos, process types, or all dynos. Reset dyno states selectively. | 21c16cf00dac |
| pipelines_create | Creates new Heroku deployment pipeline with configurable stages, apps, and team settings | 886834e6b934 |
| pipelines_promote | Promotes apps between pipeline stages with configurable target applications | 71bb50877888 |
| pipelines_list | Lists accessible Heroku pipelines with ownership and configuration details | d0edc0af99ef |
| pipelines_info | Displays detailed pipeline configuration, stages, and connected applications | fbc98daf7d1e |
| deploy_to_heroku | Use for all deployments. Deploys new/existing apps, with or without teams/spaces, and env vars to Heroku. Ask for app name if missing. Requires valid app.json via appJson param. | 5e1818dbc540 |
| deploy_one_off_dyno | Run code/commands in Heroku one-off dyno with network and filesystem access. Requirements: - Show command output - Use app_info for buildpack detection - Support shell setup commands - Use stdout/stderr Features: - Network/filesystem access - Environment variables - File operations - Temp directory handling Usage: 1. Use Heroku runtime 2. Proper syntax/imports 3. Organized code structure 4. Package management: - Define dependencies - Minimize external deps - Prefer native modules Example package.json: ```json { "type": "module", "dependencies": { "axios": "^1.6.0" } } ``` | 4f6c4b7f5cb7 |
Lock these tools
Pin what @heroku/mcp-server serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock# .github/workflows/verfy.yml, after actions/checkout
- uses: anvarbekovjavohir277-dot/verfy-action@v1Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.