Can I use Heroku as a CLI?

Yes. KosmoKrator exposes a Heroku CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Heroku through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Heroku tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Heroku credentials stored?

Heroku credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Heroku MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Heroku CLI for Cron Jobs

Use the Heroku CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write API key auth

Submit Heroku feedback View package source

Heroku CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Heroku CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Heroku CLI for Cron Jobs
kosmokrator integrations:configure heroku --set api_key="$HEROKU_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call heroku.heroku_list_apps '{}' --json

Discovery Before Execution

Agents and scripts can inspect Heroku docs and schemas before choosing a function.

kosmo integrations:docs heroku --json
kosmo integrations:docs heroku.heroku_list_apps --json
kosmo integrations:schema heroku.heroku_list_apps --json
kosmo integrations:search "Heroku" --json
kosmo integrations:list --json

Useful Heroku CLI Functions

Function	Type	Parameters	Description
`heroku.heroku_list_apps`	Read	none	List all Heroku apps the authenticated user has access to. Returns app names, IDs, regions, and status.
`heroku.heroku_get_app`	Read	app_id	Get details for a specific Heroku app by ID or name. Returns full app information including region, stack, and Git URL.
`heroku.heroku_list_dynos`	Read	app_id	List all dynos for a given Heroku app. Returns dyno names, types, sizes, states, and uptime.
`heroku.heroku_list_addons`	Read	app_id	List all add-ons attached to a given Heroku app. Returns add-on names, plans, states, and provider details.
`heroku.heroku_list_domains`	Read	app_id	List all domains for a given Heroku app. Returns domain hostnames, types (custom/Heroku), and status.
`heroku.heroku_list_collaborators`	Read	app_id	List all collaborators for a given Heroku app. Returns collaborator emails, roles, and permissions.
`heroku.heroku_get_current_user`	Read	none	Get information about the current authenticated Heroku account, including email, name, and verified status.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Heroku CLI Pages

CI Heroku CLI for CI. Shell Scripts Heroku CLI for shell scripts. Headless Automation Heroku CLI for headless automation. Coding Agents Heroku CLI for coding agents.