Can AI agents automate Heroku?

Heroku Platform is automatable today through the public Platform API and the official Heroku CLI. This record is Heroku apps, dynos, add-ons, pipelines, teams and spaces, and Heroku Postgres as a PaaS. It is not Salesforce CRM, not AWS, and not a generic Salesforce product identity. Clients call https://api.heroku.com over HTTPS with Accept: application/vnd.heroku+json; version=3. Personal scripts authenticate with an API token in Authorization: Bearer; HEROKU_API_KEY is the documented environment-variable form. OAuth 2.0 is the preferred mechanism for third-party access, with web authorization at id.heroku.com and direct authorizations for non-expiring personal tokens. Documented resources include apps, add-ons, config vars, domains, dynos, formations, pipelines, teams, spaces, and app webhooks. Coverage is the platform control plane, not every Dashboard action. The official heroku CLI installs on macOS, Windows, and Linux, authenticates with heroku login or HEROKU_API_KEY, and documents --json output on many commands. The heroku/platform-api Ruby gem is an official schema-generated HTTP client. App webhooks POST signed JSON for builds, releases, add-ons, dynos, and related events. Official STDIO MCP is launched with heroku mcp:start (CLI v10.8.1+) or npx -y @heroku/mcp-server and HEROKU_API_KEY. Dev Center labels that server early development and lists tools for apps, dynos, add-ons, logs, pipelines, teams and spaces, and Heroku Postgres including pg_psql. A remote mcp.heroku.com transport was not opened and is not recorded. Connector catalogs were not opened. Computer-use viability is unassessed. API and CLI both score 8; API is the best path because it is the portable documented contract and does not require a local CLI install. MCP scores 6 because the official server is useful but labeled early development.

Best path today: api · Overall automatability: 8/10