Last updated June 24, 2025

The Heroku Remote MCP Server is a Model Context Protocol (MCP) implementation that enables you to connect AI agents to the Heroku platform. This remote MCP server offers a centrally managed and secure alternative to locally run STDIO MCP servers. It uses OAuth 2.0 authentication to connect to clients, giving you full control over which applications can access your resources. With this remote MCP server, your agent can work on apps in your Heroku account.

Connect Your MCP Client to Heroku

To connect your MCP client to Heroku’s remote MCP server:

1. Follow your client’s documentation to add a new MCP server with the URL https://mcp.heroku.com/mcp.
2. Log in to your Heroku account when prompted to authenticate.

Your client is now securely connected and ready to use.

Connect to Claude.ai

1. Log in to Claude.ai.
2. In the Claude dashboard, select Settings then select Integrations.
3. Select Add Server.
4. Enter “Heroku” as the Name and https://mcp.heroku.com/mcp as the URL.
5. Follow the prompts to authenticate into your Heroku account with OAuth 2.0.

Connect to Claude Desktop

You can connect to Claude Desktop with a proxy command:

1. Open the config file:
   • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: C:\Users\<YourUsername>\AppData\Roaming\Claude\claude_desktop_config.json

2. Add the following to the mcpServers object:

   {
       "mcpServers": {
         "Heroku": {
           "command": "npx",
           "args": ["-y", "mcp-remote", "https://mcp.heroku.com/mcp"]
         }
       }
   }
   

3. Restart the Claude desktop app.

Troubleshooting

If you’re having trouble connecting an MCP client to mcp.heroku.com:

• Ensure your MCP client supports Streamable HTTP, which is a newer standard than server-sent events (SSE).
• Confirm you have permission to add https://mcp.heroku.com/mcp with clients that restrict this access, for example, Claude Enterprise and Team plans.
• Confirm your client has an extension installed to rewrite MCP server URLs, for example, Cursor).

Authorization Issues

MCP clients must support web-based OAuth flow to connect to mcp.heroku.com. With web-based OAuth flow, users are asked to authenticate with the server’s identity provider (id.heroku.com) when the client opens a default browser window. After successful authorization, the client maintains the connection using OAuth token refresh.

If an established connection to the remote MCP server hangs, continuously retries, or is otherwise broken, you may need to reset your client’s authorization.

Reset Auth for Cursor

1. In the web browser, clear cookies for the MCP server origin mcp.heroku.com.
2. Open Cursor.
3. Open the Command palette (Cmd+Shift+P).
4. Select Cursor: Clear All MCP Tokens.
5. Restart Cursor.
6. Ensure that the MCP server configuration is the correct URL https://mcp.heroku.com/mcp (some extensions may alter configured URLs).
7. Enable the MCP server and click Login.

Reset Auth for mcp-remote Clients

For clients based on mcp-remote library, like mcp-inspector:

1. In the web browser, clear cookies for the MCP server origin mcp.heroku.com.
2. Quit the mcp-remote client.
3. In the terminal/shell, execute rm -rf ~/.mcp-auth.
4. Start the client and proceed with login.

Reset Auth for Other Clients

Generally, if an established MCP server connection is failing:

1. In the web browser, clear cookies for the MCP server origin, mcp.heroku.com.
2. Open your client.
   1. Remove the MCP server configuration.
   2. Restart the client.
   3. Recreate the MCP server config.
   4. Initiate the login flow.

Authorization behavior for MCP clients isn’t standardized. Reach out to the developer or publisher of your MCP client for support on how to reset configuration and authorization for remote MCP servers as necessary.

Customer Support

You can submit issues via one of our Heroku Support channels.

Additional Resources

• STDIO MCP Servers
• Working With MCP on Heroku