Heroku integration
Cloud platform for building, deploying, and managing applications
Say what should happen.
The workflow builds itself.
Common Heroku use cases
- Set API keys
- Add custom domain
- Check dyno health
- CI/CD deployments
- Check build status
- Remove old domains
- Set up new project
- View all pipelines
- View build history
- Check current scaling
What you can do with Heroku
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
App, 5 operations
create_appCreate appPOSTCreate a new Heroku application.delete_appDelete appDELETEDelete a Heroku application permanently.get_appGet appGETGet application details by name or ID.list_appsList appsGETList all Heroku applications.update_appUpdate appPATCHUpdate application settings.
Addon, 3 operations
create_addonCreate addonPOSTProvision a new add-on service.delete_addonDelete addonDELETEDelete an add-on from an application.list_addonsList addonsGETList application add-ons.
Build, 3 operations
create_buildCreate buildPOSTTriggers a new build from a source tarball.get_buildGet buildGETRetrieves details of a specific build.list_buildsList buildsGETList all builds for an application.
Domain, 3 operations
add_domainAdd domainPOSTAdd a custom domain to an application.delete_domainDelete domainDELETERemove a custom domain from an application.list_domainsList domainsGETList custom domains for app.
Dyno, 3 operations
list_dynosList dynosGETList running dynos for application.restart_dynosRestart dynosDELETERestart all application dynos.run_dynoRun dynoPOSTRuns a one-off dyno command for maintenance or admin tasks.
Config var, 2 operations
get_config_varsGet config varsGETGet application environment variables.update_config_varsUpdate config varsPATCHSet or update environment variables.
Formation, 2 operations
get_formationGet formationGETRetrieves the dyno formation configuration for an app.scale_formationScale formationPATCHScale dyno count and size.
Release, 2 operations
create_releaseCreate releasePOSTCreate a new release by deploying a slug.list_releasesList releasesGETList application release history.
Log, 1 operation
get_logsGet logsPOSTCreate log session for app logs.
Pipeline, 1 operation
list_pipelinesList pipelinesGETRetrieves all pipelines in the account.
Promotion, 1 operation
promote_pipelinePromote pipelinePOSTPromotes an app from one pipeline stage to another.
Use Heroku from Claude Code, Cursor or Codex
Connect Heroku in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Heroku operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Heroku
- Create your workspace
Sign up free. Nothing to install.
- Connect Heroku once
Add your Heroku connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Heroku integration FAQ
What can you do with the Heroku integration?
LiveContext exposes 26 operations on Heroku, covering app, addon, build and domain. Common uses include Set API keys, Add custom domain and Check dyno health.
