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 Headless Automation

Use the Paddle CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Paddle feedback View package source

Paddle CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Paddle CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Paddle CLI for Headless Automation
kosmokrator integrations:configure paddle --set access_token="$PADDLE_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call paddle.paddle_list_transactions '{"limit":1,"after":"example_after","status":"example_status","customer_id":"example_customer_id"}' --json

Discovery Before Execution

Agents and scripts can inspect Paddle docs and schemas 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

Useful Paddle CLI Functions

Function	Type	Parameters	Description
`paddle.paddle_list_transactions`	Read	limit, after, status, customer_id	List Paddle transactions. Supports filtering by status and customer ID, with cursor-based pagination.
`paddle.paddle_get_transaction`	Read	id	Get detailed information about a specific Paddle transaction by its ID.
`paddle.paddle_list_customers`	Read	limit, after, email, name	List Paddle customers. Supports filtering by email and name, with cursor-based pagination.
`paddle.paddle_get_customer`	Read	id	Get detailed information about a specific Paddle customer by their ID.
`paddle.paddle_create_customer`	Write	email, name	Create a new customer in Paddle. An email address is required.
`paddle.paddle_list_products`	Read	limit, after, status	List Paddle products. Supports filtering by status with cursor-based pagination.
`paddle.paddle_get_current_user`	Read	none	Verify Paddle API connectivity by performing a health check request. Returns connection status and API response.

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 Paddle CLI Pages

CI Paddle CLI for CI. Cron Jobs Paddle CLI for cron jobs. Shell Scripts Paddle CLI for shell scripts. Coding Agents Paddle CLI for coding agents.