Heroku: MCP server, CLI and agent surfaces
Sign-in required, tools not seen, not counted. No source names an endpoint for Heroku; the connector's guess at mcp.heroku.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in.
Fact sheet
| Company | Heroku |
|---|
| Domain | heroku.com |
|---|
| Category | Infrastructure (Ora leaderboard category) |
|---|
| MCP server | Sign-in required (OAuth with client registration) |
|---|
| Tranco rank | 5,541 on the list of 4 November 2026 |
|---|
| Ora score | 73, grade B; Ora scanned the domain on 1 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for heroku.com, a vendor-published score) |
|---|
| Company found through | the vendor's own documentation; Ora's public leaderboard |
|---|
| Last verified | 4 November 2026 |
|---|
MCP server
| Endpoint | https://mcp.heroku.com/mcp |
|---|
| How it was found | endpoint found by subdomain guess; it answered with a sign-in challenge and was not verified |
|---|
| Transport | streamable-http |
|---|
| HTTP status | 401 |
|---|
| Connected | 4 November 2026, 20:01 UTC |
|---|
| Handshake time | 1,412 ms over 1 attempt |
|---|
| Documentation | devcenter.heroku.com |
|---|
The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools.
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:56:08Z https://mcp.heroku.com/mcp sent initialize result auth-required (HTTP 401) 1241 ms
- 20:01:46Z https://mcp.heroku.com/mcp sent initialize result auth-required (HTTP 401) 1412 ms
Authentication
| Auth type | OAuth with client registration |
|---|
| What the challenge said | Bearer error="invalid_token", error_description="Missing Authorization header" |
|---|
| Protected resource metadata | mcp.heroku.com |
|---|
| Authorization server metadata | mcp.heroku.com |
|---|
| Registration endpoint | https://mcp.heroku.com/reg |
|---|
The sign-in route, step by step
- Request
https://mcp.heroku.com/mcp without a token. It answers 401 and a WWW-Authenticate header. - Read the protected resource metadata at
https://mcp.heroku.com/.well-known/oauth-protected-resource to find the authorization server. - Register a client at the registration endpoint
https://mcp.heroku.com/reg (dynamic client registration), so no human has to create an app first. - Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
| Package | heroku on npm (page) |
|---|
| Exists | yes |
|---|
| Latest version | 11.12.1 |
|---|
| Last publish | 22 October 2026 |
|---|
| Command names | heroku |
|---|
| Checked | 4 November 2026 |
|---|
Other agent surfaces
Agent surfaces other than MCP and CLI| Surface | Result |
|---|
| OpenAPI file | No OpenAPI file at the root paths checked. |
| WebMCP in the initial HTML | Not detected on the home page by the shared crawl. |
| MCP discovery file | Not found (the crawl got a non-200 answer). |
| A2A agent card | Not found (the crawl got a non-200 answer). |
| A2A agent card (older path) | Not found (the crawl got a non-200 answer). |
| agents.json | Not found (the crawl got a non-200 answer). |
| OAuth authorization server metadata | Not found (the crawl got a non-200 answer). |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
Registry listings| Registry | Listed |
|---|
| Official MCP Registry | No |
| GitHub MCP Registry | No |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |