Kiwi for Heroku
Have the agent on a Kiwi step check a Heroku app's dynos, logs and Postgres database, through Heroku's MCP server.
- Your agent works in Heroku through its own connection. Kiwi does not call Heroku and never holds its credentials.
- A workflow skill can list Heroku among the tools it requires. When you supply your agent's available tools to a skill check and Heroku is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Heroku, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Heroku connection, with
report_configuration. - The agent submits links to its work in Heroku as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Heroku
- List apps and read an app's details, dynos and logs.
- Deploy an app, and scale or restart its dynos.
- Promote a release to the next stage of a pipeline.
- Turn maintenance mode on or off.
- Read Heroku Postgres details, slow queries, locks and backups.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Heroku
Add the Heroku MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.heroku.com/mcpExample skill
Publish instructions like these as a workflow skill that lists Heroku among its required tools.
Read the Heroku app name and the pipeline from the run's inputs. In Heroku, check the staging app's dynos and its logs since the last deploy, then read the slow queries of its Postgres database. Submit the release version, the log excerpts and the slow queries as outputs. Promoting to production or scaling dynos is for the run's Owner. Report a blocker if the staging app has crashed.