Heroku MCP server

Official

get_addon_info

Retrieve detailed information about a Heroku add-on, including plan state, billing details, and configuration. Supports identifiers like add-on ID, name, or attachment name, requiring app context for attachments.

Instructions

Get comprehensive information about a Heroku add-on. Use this tool when you need to: 1) View add-on details, 2) Check plan details and state, 3) View billing information. Accepts add-on ID, name, or attachment name.

Input Schema

NameRequiredDescriptionDefault
addonYesIdentifies the add-on to retrieve information about. Accepts three types of identifiers: 1) Add-on ID (uuid format, works globally without app context), 2) Add-on name (e.g., "postgresql-curved-12345", works globally without app context), 3) Attachment name (e.g., "DATABASE", requires app context). Important behaviors: - When using attachment name, must provide app flag or have default app set, - Attachment name must be from the app where attached, not the provisioning app, - Add-on ID and unique names work with correct app context or without app context, - Must have access to the app where the add-on is either provisioned or attached.
appNoProvides application context for finding the add-on. Affects how the addon parameter is interpreted: 1) When provided: - Searches for the add-on only within this specific app, - Enables use of attachment names in the addon parameter, - Must have access to this app. 2) When omitted: - First tries using default app from Git remote configuration, - If no default app, addon parameter must be an ID or globally unique name, - Cannot use attachment names without app context. Best practice: Always provide when using attachment names.

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "addon": { "description": "Identifies the add-on to retrieve information about. Accepts three types of identifiers: 1) Add-on ID (uuid format, works globally without app context), 2) Add-on name (e.g., \"postgresql-curved-12345\", works globally without app context), 3) Attachment name (e.g., \"DATABASE\", requires app context). Important behaviors: - When using attachment name, must provide app flag or have default app set, - Attachment name must be from the app where attached, not the provisioning app, - Add-on ID and unique names work with correct app context or without app context, - Must have access to the app where the add-on is either provisioned or attached.", "type": "string" }, "app": { "description": "Provides application context for finding the add-on. Affects how the addon parameter is interpreted: 1) When provided: - Searches for the add-on only within this specific app, - Enables use of attachment names in the addon parameter, - Must have access to this app. 2) When omitted: - First tries using default app from Git remote configuration, - If no default app, addon parameter must be an ID or globally unique name, - Cannot use attachment names without app context. Best practice: Always provide when using attachment names.", "type": "string" } }, "required": [ "addon" ], "type": "object" }
ID: c1gtn2x5d2