Heroku MCP
Manage Heroku apps, dynos and add-ons from an agent
Last verified: September 6, 2026
How to Install Heroku MCP
$npx -y @heroku/mcp-serverRequires Claude Desktop, Cursor, Windsurf, or another MCP-compatible client.
About Heroku MCP
The Heroku MCP server lets AI tools operate the Heroku Platform directly — listing and scaling dynos, inspecting logs, managing add-ons and databases, and running one-off commands. It turns routine deploy and debugging chores into instructions rather than CLI recall.
Heroku MCP is a Developer Tools MCP server designed for professional engineers and engineering teams. It enables wiring AI assistants into the inner loop of writing and shipping code by exposing Git, package, build, and CLI operations as MCP tools. Key capabilities include git and github operations (status, blame, prs), package and dependency inspection, build and test runner integration, and structured tool calls that work cleanly inside an LLM context. It integrates with Git, GitHub, GitLab, npm, pnpm, Docker, and common build systems, and is best suited for professional engineers and engineering teams who need reviewing diffs and opening prs from chat.
Key Features
- official
- deployment
- devops
- paas
- infrastructure
Pricing
- Core MCP server
- Community support
- Works with any MCP client
- Everything in Free
- Higher usage limits
- Priority support
- Everything in Pro
- SLA & SSO
- Dedicated support
Tier details are indicative — visit the Heroku MCP website for current pricing.
Pros & Cons
Pros
- Acts more like a pair programmer with real tools
- Tight scoping (one repo, dry-run) limits blast radius
- Keeps flow inside the editor
Cons
- Write operations require explicit guardrails
- Quality of output depends on repo hygiene
- Larger monorepos may need extra filtering
Best For
- Reviewing diffs and opening PRs from chat
- Triaging CI failures
- Scaffolding new packages or modules
- Repo-wide refactors with verification
Screenshots
Screenshots coming soon —
Submit yours →Our Take on Heroku MCP
Worth installing if Heroku is in your stack — log inspection and dyno scaling through an agent removes most day-to-day CLI friction. Scope credentials carefully since it can change running infrastructure.