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.

marketing

Drip CLI for Cron Jobs

Use the Drip CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write API key auth

Submit Drip feedback View package source

Drip CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Drip CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Drip CLI for Cron Jobs
kosmokrator integrations:configure drip --set api_key="$DRIP_API_KEY" --set account_id="$DRIP_ACCOUNT_ID" --enable --read allow --write ask --json
kosmo integrations:call drip.drip_list_campaigns '{"page":1,"per_page":1}' --json

Discovery Before Execution

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

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

Useful Drip CLI Functions

Function	Type	Parameters	Description
`drip.drip_list_campaigns`	Read	page, per_page	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.
`drip.drip_get_campaign`	Read	id	Fetch a single email campaign from Drip by its campaign ID. Returns full campaign details including name, status, configuration, and associated actions.
`drip.drip_list_subscribers`	Read	page, per_page	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.
`drip.drip_get_subscriber`	Read	id	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.
`drip.drip_list_workflows`	Read	page, per_page	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.
`drip.drip_get_workflow`	Read	id	Fetch a single workflow from Drip by its workflow ID. Returns full workflow details including name, status, trigger configuration, and associated actions.
`drip.drip_get_current_user`	Read	none	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.

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 Drip CLI Pages

CI Drip CLI for CI. Shell Scripts Drip CLI for shell scripts. Headless Automation Drip CLI for headless automation. Coding Agents Drip CLI for coding agents.