Schema | MCP Heroku Server

MCP Heroku Server

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'.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/globodai-group/mcp-heroku'

If you have feedback or need assistance with the MCP directory API, please join our Discord server