Add to Docker Desktop
Version 4.43 or later needs to be installed to add the server automatically
Tools
| Name | Description |
|---|---|
create_addon | Create add-on: specify service, plan, custom names |
create_app | Create app: custom name, region (US/EU), team, private space |
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" } } ``` |
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. |
get_addon_info | Get add-on details: plan, state, billing |
get_app_info | Get app details: config, dynos, addons, access, domains |
get_app_logs | App logs: monitor/debug/filter by dyno/process/source |
list_addon_plans | List service plans: features, pricing, availability |
list_addon_services | List available add-on services and features |
list_addons | List add-ons: all apps or specific app, detailed metadata |
list_apps | List Heroku apps: owned, collaborator access, team/space filtering |
list_private_spaces | Lists Heroku Private Spaces with CIDR blocks, regions, compliance and capacity details. JSON output supported. |
list_teams | Lists accessible Heroku Teams. Use for: viewing teams, checking membership, getting team metadata, and verifying access. JSON output available. |
maintenance_off | Disable maintenance mode and restore normal app operations |
maintenance_on | Enable maintenance mode and redirect traffic for a Heroku app |
pg_backups | Manage backups: schedules, status, verification, recovery |
pg_credentials | Manage access: credentials, permissions, security, monitoring |
pg_info | View database status: config, metrics, resources, health |
pg_kill | Stop processes: stuck queries, blocking transactions, runaway operations |
pg_locks | Analyze locks: blocked queries, deadlocks, concurrency |
pg_maintenance | Track maintenance: windows, schedules, progress, planning |
pg_outliers | Find resource-heavy queries: performance, patterns, optimization |
pg_ps | Monitor active queries: progress, resources, performance |
pg_psql | Execute SQL queries: analyze, debug, modify schema, manage data |
pg_upgrade | Upgrade PostgreSQL: version migration, compatibility, safety |
pipelines_create | Creates new Heroku deployment pipeline with configurable stages, apps, and team settings |
pipelines_info | Displays detailed pipeline configuration, stages, and connected applications |
pipelines_list | Lists accessible Heroku pipelines with ownership and configuration details |
pipelines_promote | Promotes apps between pipeline stages with configurable target applications |
ps_list | List and monitor Heroku app dynos. View running dynos, check status/health, monitor process states, verify configurations. |
ps_restart | Restart Heroku app processes. Restart specific dynos, process types, or all dynos. Reset dyno states selectively. |
ps_scale | Scale Heroku app dynos. Adjust quantities, change sizes, view formation details, manage resources. |
rename_app | Rename app: validate and update app name |
transfer_app | Transfer app ownership to user/team |
Manual installation
You can install the MCP server using:
Installation for