Can I use Chargify as a CLI?

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

Can I expose Chargify through MCP?

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

Where are Chargify credentials stored?

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

Can I deny write access for Chargify MCP tools?

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

payments

Chargify MCP Integration for Cursor

Connect Chargify to Cursor through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 7 read 0 write API key auth

Submit Chargify feedback View package source

Connect Chargify to Cursor

Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server.

Create or update .cursor/mcp.json with a KosmoKrator stdio server entry. The gateway is local, scoped to this integration, and starts with --write=deny so Cursor can inspect read-capable tools without receiving write access by default.

Chargify MCP Config for Cursor

Use the same KosmoKrator install and integration credentials that power terminal and headless runs.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Chargify instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Chargify Tools Visible to Cursor

Cursor sees stable MCP tool names generated from the Chargify integration catalog.

MCP tool	Source function	Type	Description
`integration__chargify__chargify_list_subscriptions`	`chargify.chargify_list_subscriptions`	Read	List subscriptions from Chargify. Supports filtering by state (active, past_due, canceled, expired, trial, etc.) and pagination.
`integration__chargify__chargify_get_subscription`	`chargify.chargify_get_subscription`	Read	Get detailed information for a single Chargify subscription by ID.
`integration__chargify__chargify_list_customers`	`chargify.chargify_list_customers`	Read	List customers from Chargify. Supports pagination with page and per_page parameters.
`integration__chargify__chargify_get_customer`	`chargify.chargify_get_customer`	Read	Get detailed information for a single Chargify customer by ID.
`integration__chargify__chargify_list_products`	`chargify.chargify_list_products`	Read	List products available in Chargify. Supports pagination with page and per_page parameters.
`integration__chargify__chargify_list_invoices`	`chargify.chargify_list_invoices`	Read	List invoices from Chargify. Supports filtering by status (open, paid, pending, voided) and pagination.
`integration__chargify__chargify_get_current_user`	`chargify.chargify_get_current_user`	Read	Get the currently authenticated Chargify user. Useful for verifying API credentials.

Related Chargify Pages

Chargify CLIUse direct JSON commands instead of MCP discovery. Chargify MCPFull gateway reference and MCP tool names. KosmoKrator for CursorClient-level gateway setup.