Can I use ChurnZero as a CLI?

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

Can I expose ChurnZero through MCP?

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

Where are ChurnZero credentials stored?

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

Can I deny write access for ChurnZero MCP tools?

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

sales

ChurnZero CLI for Headless Automation

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

7 functions 7 read 0 write API key auth

Submit ChurnZero feedback View package source

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

Command Shape

# ChurnZero CLI for Headless Automation
kosmokrator integrations:configure churnzero --set api_key="$CHURNZERO_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call churnzero.churnzero_list_accounts '{"search":"example_search","page":1,"perPage":1}' --json

Discovery Before Execution

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

kosmo integrations:docs churnzero --json
kosmo integrations:docs churnzero.churnzero_list_accounts --json
kosmo integrations:schema churnzero.churnzero_list_accounts --json
kosmo integrations:search "ChurnZero" --json
kosmo integrations:list --json

Useful ChurnZero CLI Functions

Function	Type	Parameters	Description
`churnzero.churnzero_list_accounts`	Read	search, page, perPage	Search and list accounts in ChurnZero. Use the search parameter to filter accounts by name or other attributes. Returns a paginated list of accounts with their details.
`churnzero.churnzero_get_account`	Read	id	Get full details for a single account in ChurnZero, including health score, license information, custom fields, and associated data.
`churnzero.churnzero_list_contacts`	Read	account_id, search, page, perPage	List contacts in ChurnZero. Optionally filter by account ID to get contacts for a specific account, or use search to find contacts by name or email. Supports pagination.
`churnzero.churnzero_get_contact`	Read	id	Get full details for a single contact in ChurnZero, including email, phone, role, account association, and custom fields.
`churnzero.churnzero_list_alerts`	Read	account_id, status, page, perPage	List alerts in ChurnZero — risk signals, usage drops, renewal reminders, and other notifications. Filter by account ID or alert status. Supports pagination.
`churnzero.churnzero_list_usage`	Read	account_id, feature, page, perPage	List usage data in ChurnZero — track how customers engage with your product features. Filter by account ID or specific feature/module name. Supports pagination.
`churnzero.churnzero_get_current_user`	Read	none	Get the profile of the currently authenticated ChurnZero user — name, email, role, tenant, and other account 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 ChurnZero CLI Pages

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