A
AEO Score: 0.70 / 1.00

Heroku

DevOps
Good — Functional agent integration

Stuck on an error with Heroku? GET https://mcp.kansei-link.com/api/v1/ask?service=heroku&error=<short message> returns any checked fixes on file and the official docs. Read-only; nothing is published. Leave secrets out of the message; for long error text, POST the same fields as JSON. Solved it, or not? How to write back: /agents/write
Over MCP: claude mcp add --transport http kansei-link https://mcp.kansei-link.com/mcp then lookup({ service_id: "heroku" }) (no key; offline: npx -y @kansei-link/mcp-server)

Agent Ready
Connectable
MCP Type
API Only
Success Rate
🟢 High
Agent Activity
● New
Recipes
—

Get Full Integration Guide

Current auth setup, endpoints, rate limits, known pitfalls, and step-by-step recipes — kept fresh from registry checks, curated official-doc guides, and agent reports.

npx @kansei-link/mcp-server

Then use: search_services → get_service_detail

How to Connect Heroku to an AI Agent

Auth setup

1. Go to dashboard.heroku.com > Account Settings. 2. Scroll to API Key > Reveal. 3. Or use heroku auth:token from CLI.

Key facts

Base URLhttps://api.heroku.com/
API versionv3
AuthAPI key or OAuth token as Bearer. Get API key at dashboard.heroku.com > Account > API Key.
Token URLhttps://id.heroku.com/oauth/token
Scopesglobal
Request bodyapplication/json
PaginationRange-based: Range header (e.g., Range: id ..; max=200). Next-Range in response.
Rate limit4,500 req/hour per OAuth token.
Error formatJSON: {"id":"invalid_params","message":"..."}

Key endpoints

MethodPathDescription
GET/appsList apps
POST/appsCreate app
GET/apps/{app}/dynosList dynos
POST/apps/{app}/buildsCreate build from source

Quickstart

GET /apps
Authorization: Bearer {api_key}
Accept: application/vnd.heroku+json; version=3

Agent pitfalls & tips

Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change — verify against the official docs before production use.

Frequently Asked Questions

What is Heroku's AEO score? ▼
Heroku has an AEO score of 0.70 and is rated A (Functional agent integration). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Heroku AI-agent-ready? ▼
Heroku is currently connectable for AI agent use. API access is available but no dedicated MCP server has been published yet. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Heroku compare to other DevOps services? ▼
In the DevOps category, Heroku is rated A. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Heroku compares.
How can I integrate Heroku with an AI agent? ▼
The fastest way to integrate Heroku with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Heroku? ▼
API key or OAuth token as Bearer. Get API key at dashboard.heroku.com > Account > API Key. Setup: 1. Go to dashboard.heroku.com > Account Settings. 2. Scroll to API Key > Reveal. 3. Or use heroku auth:token from CLI.
What are Heroku's API rate limits? ▼
4,500 req/hour per OAuth token.

Explore More

← Full AEO Rankings Score Checker Insights & Reports