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.

productivity

ChurnZero MCP, CLI, and Lua Integration for AI Agents

ChurnZero integration docs for AI agents: MCP gateway setup, ChurnZero CLI commands, Lua API reference, credentials, and function schemas.

ChurnZero for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

ChurnZero CLIHeadless setup, JSON output, direct function calls. ChurnZero MCPExpose selected tools to local MCP clients. ChurnZero LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: churnzero
route_slug: churnzero
package: churnzero
auth_strategy: api_key_query
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Parameters	Description
`churnzero.churnzero_set_attributes`	Write `write`	4	Set one or more ChurnZero account or contact attributes. For contacts, provide both account_external_id and contact_external_id. Attribute names must already exist in ChurnZero where required.
`churnzero.churnzero_track_event`	Write `write`	6	Track a ChurnZero event for an account and optionally a contact. Event names are created by ChurnZero if they do not already exist.
`churnzero.churnzero_increment_attribute`	Write `write`	5	Increment a numeric ChurnZero account or contact attribute. Use a negative amount to decrement.
`churnzero.churnzero_delete_contact`	Write `write`	2	Delete a ChurnZero contact by account_external_id and contact_external_id. This action is destructive.
`churnzero.churnzero_delete_account`	Write `write`	1	Delete a ChurnZero account by account_external_id. This action is destructive and may affect related contacts.
`churnzero.churnzero_send_action`	Write `write`	1	Send an advanced raw ChurnZero HTTP API action. Do not include appKey; the integration adds credentials automatically.