MCP Heroku Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEROKU_API_KEY | Yes | Your Heroku API key, available from the Heroku Dashboard Account Settings or by running 'heroku auth:token'. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| heroku_list_appsB | List all Heroku apps. Optionally filter by team. |
| heroku_get_appC | Get detailed information about a Heroku app including dynos and formation. |
| heroku_list_releasesC | List releases for a Heroku app. Shows deployment history. |
| heroku_get_logsC | Get recent logs from a Heroku app. Can filter by dyno or source. |
| heroku_restartB | Restart dynos for a Heroku app. Can restart all dynos or a specific one. |
| heroku_scaleC | Scale dynos for a Heroku app. Change the number of running dynos. |
| heroku_list_addonsA | List all add-ons attached to a Heroku app (databases, caches, etc.) |
| heroku_config_varsC | Get or set config vars (environment variables) for a Heroku app. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose targeting specific Heroku operations: config vars, app details, logs, add-ons, app listing, releases, restarting, and scaling. There is no overlap in functionality, and an agent can easily distinguish between them based on their specific resource and action combinations.
All tool names follow a consistent 'heroku_' prefix with a verb_noun pattern (e.g., heroku_get_app, heroku_list_addons). The naming is uniform across all eight tools, using snake_case throughout, making it predictable and easy to understand.
With 8 tools, this server is well-scoped for managing Heroku apps. Each tool serves a distinct and essential function in app management, covering monitoring, configuration, deployment, and scaling without being overly broad or too limited.
The tool set provides strong coverage for core Heroku app management, including monitoring (logs, releases), configuration (config vars, add-ons), and operations (restart, scale). A minor gap exists in CRUD operations for apps (e.g., create or delete an app), but agents can still handle most workflows effectively with the available tools.