Heroku MCP Server

Heroku's MCP server connects AI agents to Heroku applications, enabling dyno scaling, app configuration inspection, add-on provisioning, and release pipeline inspections. It empowers agents to automate application deployments, monitor app logs, and manage cloud application runtimes smoothly.

Start for free

Heroku MCP Server

Benefits with Ory + Heroku MCP Server

Heroku's MCP server lets your agents manage Heroku apps, including deploys, dynos, add-ons, config vars, logs, and Heroku Postgres. Config vars often hold secrets, and dyno changes affect live traffic. Ory Agent Security lets support agents read logs and app status while changes stay with the deployment agents you approve, and every tool call is tied to the user behind it.

View documentation

Use Cases

— 01 use case

Agent IAM

Diagnostic agents read at Read, app creators use Write, deploys, scaling and SQL belong to Admin, and you Block every agent without Heroku duties.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Heroku MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for support agents reading logs, write for agents setting up new apps, admin for deployment agents, and no access for agents with no role in your apps.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied deploy stops before it reaches Heroku, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents deploy, scale, or query databases and for whom without blocking anything, so you can apply Ory's pre-built policy for the Heroku MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Heroku MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent shipped a release and which user it acted for.