cogny cliemailfirst 15 calls free

    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 the first calls (uses your git email)npx @cogny/cli init --agent claude-code
    • 2. see every Klaviyo toolcogny tools list
    • 3. call any tool from bash, no MCP wiringcogny tools call mcp__Klaviyo__get_campaign_values_report --input '{…}'
    01two paths
    you're a person

    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 a scheduled loop, do the querying for you.

    Start Solo
    you're an agent

    Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Klaviyo tool over JSON-RPC. The first 15 calls are free.

    • npx @cogny/cli init --agent claude-code
    02tools call

    real Klaviyo tools.

    Tool names as the Klaviyo MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

    • mcp__Klaviyo__get_campaign_values_report

      Performance 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_segments

      List 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_status

      Turn 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"
        }
      }
    03tools list

    the rest of the surface.

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

    • mcp__Klaviyo__list_profiles
    • mcp__Klaviyo__list_lists
    • mcp__Klaviyo__subscribe_profiles
    • mcp__Klaviyo__list_campaigns
    • mcp__Klaviyo__create_campaign
    • mcp__Klaviyo__create_segment
    • mcp__Klaviyo__list_flows
    • mcp__Klaviyo__list_metrics
    • mcp__Klaviyo__list_events
    04then a verdict

    calls from a script. verdicts from cogny.

    Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

    • worked

      Moved the number. Every measured win has a share card.

    • partial

      Some of it did.

    • didn't work

      On the record anyway, so it isn't proposed again.

    • inconclusive

      Not enough data to call.

    How the loop works

    05questions

    questions.

    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.
    06related

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

    klaviyo, then a verdict.