Can I use Drip as a CLI?

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

Can I expose Drip through MCP?

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

Where are Drip credentials stored?

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

Can I deny write access for Drip MCP tools?

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

productivity

Drip CLI for AI Agents

Use the Drip CLI from KosmoKrator to call Drip tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Drip CLI Setup

Drip can be configured headlessly with `kosmokrator integrations:configure drip`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure drip --set api_key="$DRIP_API_KEY" --set account_id="$DRIP_ACCOUNT_ID" --enable --read allow --write ask --json
kosmokrator integrations:doctor drip --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`api_key`	`DRIP_API_KEY`	Secret `secret`	yes	API Key
`account_id`	`DRIP_ACCOUNT_ID`	Text `string`	yes	Account ID
`url`	`DRIP_URL`	URL `url`	no	Drip API URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call drip.drip_list_campaigns '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:drip drip_list_campaigns '{"page":1,"per_page":1}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs drip --json
kosmo integrations:docs drip.drip_list_campaigns --json
kosmo integrations:schema drip.drip_list_campaigns --json
kosmo integrations:search "Drip" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`drip.drip_list_campaigns`

List email campaigns in your Drip account. Returns campaign details including name, status, and configuration. Paginated — use page and per_page parameters to navigate results.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call drip.drip_list_campaigns '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:drip drip_list_campaigns '{"page":1,"per_page":1}' --json

`drip.drip_get_campaign`

Fetch a single email campaign from Drip by its campaign ID. Returns full campaign details including name, status, configuration, and associated actions.

Read read

Parameters: id

Generic call

kosmo integrations:call drip.drip_get_campaign '{"id":"example_id"}' --json

Shortcut

kosmo integrations:drip drip_get_campaign '{"id":"example_id"}' --json

`drip.drip_list_subscribers`

List subscribers in your Drip account. Returns subscriber records including email, status, tags, and custom fields. Paginated — use page and per_page parameters to navigate results.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call drip.drip_list_subscribers '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:drip drip_list_subscribers '{"page":1,"per_page":1}' --json

`drip.drip_get_subscriber`

Fetch a single subscriber from Drip by their subscriber ID or email address. Returns full subscriber details including status, tags, custom fields, and subscription information.

Read read

Parameters: id

Generic call

kosmo integrations:call drip.drip_get_subscriber '{"id":"example_id"}' --json

Shortcut

kosmo integrations:drip drip_get_subscriber '{"id":"example_id"}' --json

`drip.drip_list_workflows`

List workflows in your Drip account. Returns workflow details including name, status, and trigger configuration. Paginated — use page and per_page parameters to navigate results.

Read read

Parameters: page, per_page

Generic call

kosmo integrations:call drip.drip_list_workflows '{"page":1,"per_page":1}' --json

Shortcut

kosmo integrations:drip drip_list_workflows '{"page":1,"per_page":1}' --json

`drip.drip_get_workflow`

Fetch a single workflow from Drip by its workflow ID. Returns full workflow details including name, status, trigger configuration, and associated actions.

Read read

Parameters: id

Generic call

kosmo integrations:call drip.drip_get_workflow '{"id":"example_id"}' --json

Shortcut

kosmo integrations:drip drip_get_workflow '{"id":"example_id"}' --json

`drip.drip_get_current_user`

Get the currently authenticated Drip user. Returns user profile information including name, email, and account details. Useful for verifying the API connection and identifying which account is active.

Read read

Parameters: none

Generic call

kosmo integrations:call drip.drip_get_current_user '{}' --json

Shortcut

kosmo integrations:drip drip_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

drip.drip_list_campaigns 2 parameters

Schema command

kosmo integrations:schema drip.drip_list_campaigns --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of results per page, max 1000 (default: 100).

drip.drip_get_campaign 1 parameters

Schema command

kosmo integrations:schema drip.drip_get_campaign --json

Parameter	Type	Required	Description
`id`	string	yes	The campaign ID.

drip.drip_list_subscribers 2 parameters

Schema command

kosmo integrations:schema drip.drip_list_subscribers --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of results per page, max 1000 (default: 100).

drip.drip_get_subscriber 1 parameters

Schema command

kosmo integrations:schema drip.drip_get_subscriber --json

Parameter	Type	Required	Description
`id`	string	yes	The subscriber ID or email address.

drip.drip_list_workflows 2 parameters

Schema command

kosmo integrations:schema drip.drip_list_workflows --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`per_page`	integer	no	Number of results per page, max 1000 (default: 100).

drip.drip_get_workflow 1 parameters

Schema command

kosmo integrations:schema drip.drip_get_workflow --json

Parameter	Type	Required	Description
`id`	string	yes	The workflow ID.

drip.drip_get_current_user 0 parameters

Schema command

kosmo integrations:schema drip.drip_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.