Heroku Platform MCP Server
Heroku Platform MCP Server. That is what the heroku mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The Heroku Platform MCP Server is a specialized Model Context Protocol (MCP) implementation designed to facilitate seamless interaction between large language models (LLMs) and the Heroku Platform. This server provides a robust set of tools and capabilities that enable LLMs to read, manage, and operate Heroku Platform resources.
The server publishes 2 tools. What each one is for:
HEROKU_API_KEY — Your Heroku authorization token. Required for authentication with the Heroku PlatformMCP_SERVER_REQUEST_TIMEOUT — Timeout in milliseconds for command execution. Defaults to 15000 (15 seconds) if not setConfiguration is passed through the environment: HEROKU_API_KEY, DEBUG, MCP_SERVER_REQUEST_TIMEOUT, YOUR_HEROKU_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@heroku/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Heroku's toolset — HEROKU_API_KEY, MCP_SERVER_REQUEST_TIMEOUT — is a fair guide to whether it matches your workflow. It is maintained by heroku; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| HEROKU_API_KEY | Your Heroku authorization token. Required for authentication with the Heroku Platform. |
| MCP_SERVER_REQUEST_TIMEOUT | Timeout in milliseconds for command execution. Defaults to 15000 (15 seconds) if not set. |
{
"mcpServers": {
"heroku": {
"command": "heroku mcp:start"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| HEROKU_API_KEY | Credential the server authenticates with. | Yes |
| DEBUG | Configuration value read at startup. | Optional |
| MCP_SERVER_REQUEST_TIMEOUT | Configuration value read at startup. | Optional |
| YOUR_HEROKU_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.