Cogny CLI · Email

Klaviyo driven from Bash.

List profiles, lists, segments, campaigns and flows, pull campaign performance reports, and push segment or flow-status changes to Klaviyo — from the shell over the Klaviyo MCP. The Klaviyo API without juggling a private key in every request.

# 1. sign up (free for 15 calls) — uses your git email
$ npx @cogny/cli init --agent claude-code

# 2. see every Klaviyo tool
$ cogny tools list

# 3. call any tool from Bash — no MCP wiring
$ cogny tools call mcp__Klaviyo__get_campaign_values_report --input '{…}'

❯ start Cogny Solo — $9/mo@cogny/cli on npm →

❯

cogny --who

TWO PATHS

You're a human

Today you click through Klaviyo dashboards to read campaign metrics and toggle flows one at a time. The CLI returns campaign value reports and lets you flip a flow live or rebuild a segment in a single scriptable call. Connect Klaviyo once in Cogny Solo and let your coding agent — or scheduled reports — do the querying for you.

❯ start Solo

You're an agent

Self-onboard with one command. The CLI issues a key, wires nothing, and exposes every Klaviyo tool over JSON-RPC. First 15 calls are free.

$ npx @cogny/cli init --agent claude-code

❯

cogny tools call

3 EXAMPLES

Real tool names from the Klaviyo MCP. Send --input JSON, get JSON back.

mcp__Klaviyo__get_campaign_values_reportPerformance statistics (opens, clicks, conversions) for a campaign.

$ cogny tools call mcp__Klaviyo__get_campaign_values_report \
  --input '{"statistics":["opens","clicks","conversion_rate"],"timeframe":{"key":"last_30_days"},"conversion_metric_id":"RFn8sQ","campaign_id":"01HXYZ"}'

example response

{
  "data": {
    "attributes": {
      "results": [
        {
          "groupings": {
            "campaign_id": "01HXYZ"
          },
          "statistics": {
            "opens": 18422,
            "clicks": 3120,
            "conversion_rate": 0.041
          }
        }
      ]
    }
  }
}

mcp__Klaviyo__list_segmentsList segments with their definitions and profile counts.

$ cogny tools call mcp__Klaviyo__list_segments \
  --input '{}'

example response

{
  "data": [
    {
      "id": "Xq8kAb",
      "name": "Engaged 30d",
      "profile_count": 12840
    },
    {
      "id": "Yt2nCd",
      "name": "Lapsed buyers",
      "profile_count": 4210
    }
  ]
}

mcp__Klaviyo__update_flow_statusTurn a flow live or pause it.

$ cogny tools call mcp__Klaviyo__update_flow_status \
  --input '{"flow_id":"Wm5pQr","status":"live"}'

example response

{
  "data": {
    "id": "Wm5pQr",
    "status": "live"
  }
}

❯

cogny tools list

A sample of the rest of the Klaviyo surface. Run cogny tools list --json for every tool and its input schema.

mcp__Klaviyo__list_profilesmcp__Klaviyo__list_listsmcp__Klaviyo__subscribe_profilesmcp__Klaviyo__list_campaignsmcp__Klaviyo__create_campaignmcp__Klaviyo__create_segmentmcp__Klaviyo__list_flowsmcp__Klaviyo__list_metricsmcp__Klaviyo__list_events

❯

cogny --faq

Is this an official Klaviyo CLI?

No — it is the Cogny CLI calling the Klaviyo MCP over the cogny-mcp-proxy. You connect your Klaviyo private API key once inside Cogny and then call every tool from Bash.

Can it send campaigns or just read?

Both. The Klaviyo MCP exposes read tools (profiles, lists, segments, campaign reports) and write tools (create campaign/segment, subscribe profiles, change flow status). Sends still respect Klaviyo’s own review and sending rules.

Can my coding agent call these?

Yes. After `npx @cogny/cli init`, an agent runs `cogny tools call mcp__Klaviyo__get_campaign_values_report --input ...` from any shell — no MCP wiring or restart needed.

❯

related CLIs

/cli/mailchimp→/cli/brevo→/cli/shopify→

Building an agent? The full tool map for all servers is one fetch: /cli/llms.txt