KosmoKrator

other

Paddle MCP Gateway for AI Agents

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

7 functions 6 read 1 write Bearer token auth

Paddle MCP Gateway

Expose Paddle to MCP clients with `kosmokrator mcp:serve --integration=paddle`.

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=paddle --write=deny --json
{
  "mcpServers": {
    "kosmokrator-paddle": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=paddle",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

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

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP toolSource functionType
integration__paddle__paddle_list_transactions paddle.paddle_list_transactions Read read
integration__paddle__paddle_get_transaction paddle.paddle_get_transaction Read read
integration__paddle__paddle_list_customers paddle.paddle_list_customers Read read
integration__paddle__paddle_get_customer paddle.paddle_get_customer Read read
integration__paddle__paddle_create_customer paddle.paddle_create_customer Write write
integration__paddle__paddle_list_products paddle.paddle_list_products Read read
integration__paddle__paddle_get_current_user paddle.paddle_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.