Can I use Campaign Monitor as a CLI?

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

Can I expose Campaign Monitor through MCP?

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

Where are Campaign Monitor credentials stored?

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

Can I deny write access for Campaign Monitor MCP tools?

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

Campaign Monitor CLI for Cron Jobs

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

7 functions 6 read 1 write API key auth

Submit Campaign Monitor feedback View package source

Campaign Monitor 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 Campaign Monitor CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Campaign Monitor CLI for Cron Jobs
kosmokrator integrations:configure campaign-monitor --set api_key="$CAMPAIGN_MONITOR_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call campaign-monitor.campaignmonitor_list_campaigns '{}' --json

Discovery Before Execution

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

kosmo integrations:docs campaign-monitor --json
kosmo integrations:docs campaign-monitor.campaignmonitor_list_campaigns --json
kosmo integrations:schema campaign-monitor.campaignmonitor_list_campaigns --json
kosmo integrations:search "Campaign Monitor" --json
kosmo integrations:list --json

Useful Campaign Monitor CLI Functions

Function	Type	Parameters	Description
`campaign-monitor.campaignmonitor_list_campaigns`	Read	none	List all email campaigns in your Campaign Monitor account. Returns campaign IDs, subjects, and status.
`campaign-monitor.campaignmonitor_get_campaign`	Read	campaign_id	Get detailed information about a specific email campaign, including subject, content, and delivery stats.
`campaign-monitor.campaignmonitor_list_lists`	Read	none	List all subscriber lists in your Campaign Monitor account. Returns list IDs and names.
`campaign-monitor.campaignmonitor_get_list`	Read	list_id	Get detailed information about a specific subscriber list, including subscriber counts and custom fields.
`campaign-monitor.campaignmonitor_list_subscribers`	Read	list_id, page, page_size	List active subscribers on a Campaign Monitor list. Returns email addresses, names, and subscription dates.
`campaign-monitor.campaignmonitor_add_subscriber`	Write	list_id, email, name, resubscribe	Add a new subscriber to a Campaign Monitor list. The subscriber will receive a confirmation email if double opt-in is enabled.
`campaign-monitor.campaignmonitor_get_current_user`	Read	none	Get the authenticated user's Campaign Monitor account details, including name and email.

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 Campaign Monitor CLI Pages

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