[ MCP SERVER SUMMARY ]
Interact with the Heroku Platform through LLM-driven tools for managing apps, add-ons, dynos, databases, and more. Connect Heroku through Bifrost MCP Gateway to centralize access control, virtual keys, and tool-call observability for your AI assistants.
| Property | Details |
|---|---|
| Company | Upstream maintainer |
| Connection type | Confirm upstream transport |
| Authentication | Varies by upstream server |
| Package or endpoint | See upstream documentation |
| Capabilities | Heroku tools over MCP, AI assistant connectivity, Governed tool access through Bifrost |
| Official documentation | Heroku MCP documentation |
[ HOW TO CONNECT ]
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and select the transport documented by the upstream server. Or register via the API below.
• Confirm the transport, command or endpoint, and authentication requirements in the Heroku upstream documentation.
• Replace every placeholder in the example before sending the request.
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Heroku.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
# For a remote HTTP or SSE server:
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "heroku",
"connection_type": "<http|sse>",
"connection_string": "<upstream MCP endpoint>",
"tools_to_execute": ["*"]
}'
# For a local STDIO server:
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "heroku",
"connection_type": "stdio",
"stdio_config": {
"command": "<upstream command>",
"args": ["<arg>"]
},
"tools_to_execute": ["*"]
}'[ WHY BIFROST ]
Virtual keys, RBAC, and tool allowlists per team or agent.
Attribute MCP tool spend alongside LLM usage in one view.
Log every tool call with latency, server, and virtual key metadata.
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Interact with the Heroku Platform through LLM-driven tools for managing apps, add-ons, dynos, databases, and more. The exact tools available depend on the upstream server version and configuration.
Check the upstream documentation to determine whether Heroku uses STDIO, Streamable HTTP, or SSE. Then add it as an MCP client in Bifrost using the corresponding command or endpoint.
No. Bifrost connects to Heroku as an upstream MCP client and adds a governed gateway between that server and your AI assistants.