Can I use Paddle as a CLI?

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

Can I expose Paddle through MCP?

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

Where are Paddle credentials stored?

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

Can I deny write access for Paddle MCP tools?

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

other

Paddle CLI for AI Agents

Use the Paddle CLI from KosmoKrator to call Paddle tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write Bearer token auth

Submit Paddle feedback View package source

Paddle CLI Setup

Paddle can be configured headlessly with `kosmokrator integrations:configure paddle`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure paddle --set access_token="$PADDLE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor paddle --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`access_token`	`PADDLE_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`PADDLE_URL`	URL `url`	no	Paddle API URL

Call Paddle Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call paddle.paddle_list_transactions '{
  "limit": 1,
  "after": "example_after",
  "status": "example_status",
  "customer_id": "example_customer_id"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:paddle paddle_list_transactions '{
  "limit": 1,
  "after": "example_after",
  "status": "example_status",
  "customer_id": "example_customer_id"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs paddle --json
kosmo integrations:docs paddle.paddle_list_transactions --json
kosmo integrations:schema paddle.paddle_list_transactions --json
kosmo integrations:search "Paddle" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Paddle.

`paddle.paddle_list_transactions`

Read read

List Paddle transactions. Supports filtering by status and customer ID, with cursor-based pagination.

Parameters: limit, after, status, customer_id

Generic CLI call

kosmo integrations:call paddle.paddle_list_transactions '{"limit":1,"after":"example_after","status":"example_status","customer_id":"example_customer_id"}' --json

Provider shortcut

kosmo integrations:paddle paddle_list_transactions '{"limit":1,"after":"example_after","status":"example_status","customer_id":"example_customer_id"}' --json

`paddle.paddle_get_transaction`

Read read

Get detailed information about a specific Paddle transaction by its ID.

Parameters: id

Generic CLI call

kosmo integrations:call paddle.paddle_get_transaction '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:paddle paddle_get_transaction '{"id":"example_id"}' --json

`paddle.paddle_list_customers`

Read read

List Paddle customers. Supports filtering by email and name, with cursor-based pagination.

Parameters: limit, after, email, name

Generic CLI call

kosmo integrations:call paddle.paddle_list_customers '{"limit":1,"after":"example_after","email":"example_email","name":"example_name"}' --json

Provider shortcut

kosmo integrations:paddle paddle_list_customers '{"limit":1,"after":"example_after","email":"example_email","name":"example_name"}' --json

`paddle.paddle_get_customer`

Read read

Get detailed information about a specific Paddle customer by their ID.

Parameters: id

Generic CLI call

kosmo integrations:call paddle.paddle_get_customer '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:paddle paddle_get_customer '{"id":"example_id"}' --json

`paddle.paddle_create_customer`

Write write

Create a new customer in Paddle. An email address is required.

Parameters: email, name

Generic CLI call

kosmo integrations:call paddle.paddle_create_customer '{"email":"example_email","name":"example_name"}' --json

Provider shortcut

kosmo integrations:paddle paddle_create_customer '{"email":"example_email","name":"example_name"}' --json

`paddle.paddle_list_products`

Read read

List Paddle products. Supports filtering by status with cursor-based pagination.

Parameters: limit, after, status

Generic CLI call

kosmo integrations:call paddle.paddle_list_products '{"limit":1,"after":"example_after","status":"example_status"}' --json

Provider shortcut

kosmo integrations:paddle paddle_list_products '{"limit":1,"after":"example_after","status":"example_status"}' --json

`paddle.paddle_get_current_user`

Read read

Verify Paddle API connectivity by performing a health check request. Returns connection status and API response.

Parameters: none

Generic CLI call

kosmo integrations:call paddle.paddle_get_current_user '{}' --json

Provider shortcut

kosmo integrations:paddle paddle_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`paddle.paddle_list_transactions`

List Paddle transactions. Supports filtering by status and customer ID, with cursor-based pagination.

Operation: Read read
Schema command: kosmo integrations:schema paddle.paddle_list_transactions --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of transactions to return per page (default: 50).
`after`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`status`	string	no	Filter by transaction status: "completed", "pending", "billed", "paid", "canceled", "past_due".
`customer_id`	string	no	Filter transactions by customer ID.

`paddle.paddle_get_transaction`

Get detailed information about a specific Paddle transaction by its ID.

Operation: Read read
Schema command: kosmo integrations:schema paddle.paddle_get_transaction --json

Parameter	Type	Required	Description
`id`	string	yes	The Paddle transaction ID (e.g., "txn_01abc123").

`paddle.paddle_list_customers`

List Paddle customers. Supports filtering by email and name, with cursor-based pagination.

Operation: Read read
Schema command: kosmo integrations:schema paddle.paddle_list_customers --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of customers to return per page (default: 50).
`after`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`email`	string	no	Filter customers by email address.
`name`	string	no	Filter customers by name.

`paddle.paddle_get_customer`

Get detailed information about a specific Paddle customer by their ID.

Operation: Read read
Schema command: kosmo integrations:schema paddle.paddle_get_customer --json

Parameter	Type	Required	Description
`id`	string	yes	The Paddle customer ID (e.g., "ctm_01abc123").

`paddle.paddle_create_customer`

Create a new customer in Paddle. An email address is required.

Operation: Write write
Schema command: kosmo integrations:schema paddle.paddle_create_customer --json

Parameter	Type	Required	Description
`email`	string	yes	Customer email address.
`name`	string	no	Customer display name.

`paddle.paddle_list_products`

List Paddle products. Supports filtering by status with cursor-based pagination.

Operation: Read read
Schema command: kosmo integrations:schema paddle.paddle_list_products --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of products to return per page (default: 50).
`after`	string	no	Cursor for pagination — pass the value from a previous response to get the next page.
`status`	string	no	Filter by product status: "active", "archived".

`paddle.paddle_get_current_user`

Verify Paddle API connectivity by performing a health check request. Returns connection status and API response.

Operation: Read read
Schema command: kosmo integrations:schema paddle.paddle_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.