KosmoKrator

productivity

Heroku MCP Gateway for AI Agents

Expose Heroku tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

7 functions 7 read 0 write API key auth

Heroku MCP Gateway

Expose Heroku to MCP clients with `kosmokrator mcp:serve --integration=heroku`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash
kosmokrator mcp:gateway:install --integration=heroku --write=deny --json
{
  "mcpServers": {
    "kosmokrator-heroku": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=heroku",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

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

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP toolSource functionType
integration__heroku__heroku_list_apps heroku.heroku_list_apps Read read
integration__heroku__heroku_get_app heroku.heroku_get_app Read read
integration__heroku__heroku_list_dynos heroku.heroku_list_dynos Read read
integration__heroku__heroku_list_addons heroku.heroku_list_addons Read read
integration__heroku__heroku_list_domains heroku.heroku_list_domains Read read
integration__heroku__heroku_list_collaborators heroku.heroku_list_collaborators Read read
integration__heroku__heroku_get_current_user heroku.heroku_get_current_user Read read

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.