Can I use Chargebee as a CLI?

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

Can I expose Chargebee through MCP?

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

Where are Chargebee credentials stored?

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

Can I deny write access for Chargebee MCP tools?

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

payments

Chargebee CLI for Headless Automation

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

7 functions 7 read 0 write Bearer token auth

Submit Chargebee feedback View package source

Chargebee 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 Chargebee CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Chargebee CLI for Headless Automation
kosmokrator integrations:configure chargebee --set access_token="$CHARGEBEE_ACCESS_TOKEN" --set site_name="$CHARGEBEE_SITE_NAME" --enable --read allow --write ask --json
kosmo integrations:call chargebee.chargebee_list_subscriptions '{"limit":1,"page":"example_page","state":"example_state"}' --json

Discovery Before Execution

Agents and scripts can inspect Chargebee docs and schemas before choosing a function.

kosmo integrations:docs chargebee --json
kosmo integrations:docs chargebee.chargebee_list_subscriptions --json
kosmo integrations:schema chargebee.chargebee_list_subscriptions --json
kosmo integrations:search "Chargebee" --json
kosmo integrations:list --json

Useful Chargebee CLI Functions

Function	Type	Parameters	Description
`chargebee.chargebee_list_subscriptions`	Read	limit, page, state	List subscriptions from Chargebee. Supports filtering by state (active, cancelled, non_renewing, paused, in_trial, future) and pagination. Returns subscription details including plan, status, and billing period.
`chargebee.chargebee_get_subscription`	Read	id	Retrieve detailed information about a specific Chargebee subscription by its ID, including plan details, billing period, status, and associated customer.
`chargebee.chargebee_list_customers`	Read	limit, page	List customers from Chargebee with pagination. Returns customer details including email, name, company, and billing address.
`chargebee.chargebee_get_customer`	Read	id	Retrieve detailed information about a specific Chargebee customer by their ID, including contact details, billing address, and payment method.
`chargebee.chargebee_list_invoices`	Read	limit, page, status	List invoices from Chargebee. Supports filtering by status (paid, posted, payment_due, not_paid, voided, pending) and pagination.
`chargebee.chargebee_get_invoice`	Read	id	Retrieve detailed information about a specific Chargebee invoice by its ID, including line items, totals, tax, and payment status.
`chargebee.chargebee_get_current_user`	Read	none	Retrieve the current authenticated user information from Chargebee. Use this to verify credentials are working and check user details.

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

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