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 MCP Integration for Vercel AI SDK

Connect Heroku to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write API key auth

Submit Heroku feedback View package source

Connect Heroku to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Heroku MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

{
  "mcpServers": {
    "kosmokrator-heroku": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=heroku",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=heroku --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Heroku instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Heroku Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Heroku integration catalog.

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

Related Heroku Pages

Heroku CLIUse direct JSON commands instead of MCP discovery. Heroku MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.