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 MCP Gateway for AI Agents

Expose ChurnZero tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

7 functions 7 read 0 write API key auth

Submit ChurnZero feedback View package source

ChurnZero MCP Gateway

Expose ChurnZero to MCP clients with `kosmokrator mcp:serve --integration=churnzero`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

kosmokrator mcp:gateway:install --integration=churnzero --write=deny --json

{
  "mcpServers": {
    "kosmokrator-churnzero": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=churnzero",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

kosmokrator mcp:serve --integration=churnzero --write=deny

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP tool	Source function	Type
`integration__churnzero__churnzero_list_accounts`	`churnzero.churnzero_list_accounts`	Read `read`
`integration__churnzero__churnzero_get_account`	`churnzero.churnzero_get_account`	Read `read`
`integration__churnzero__churnzero_list_contacts`	`churnzero.churnzero_list_contacts`	Read `read`
`integration__churnzero__churnzero_get_contact`	`churnzero.churnzero_get_contact`	Read `read`
`integration__churnzero__churnzero_list_alerts`	`churnzero.churnzero_list_alerts`	Read `read`
`integration__churnzero__churnzero_list_usage`	`churnzero.churnzero_list_usage`	Read `read`
`integration__churnzero__churnzero_get_current_user`	`churnzero.churnzero_get_current_user`	Read `read`

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.