Cogny CLI · Email

    Drip from your shell.

    List and upsert subscribers, apply and remove tags, record events, walk Email Series campaigns and workflows, and enroll subscribers — from Bash over the Drip MCP. No API client to build, just JSON in and out.

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

# 2. see every Drip tool
$ cogny tools list

# 3. call any tool from Bash — no MCP wiring
$ cogny tools call mcp__Drip__list_subscribers --input '{…}'
    ❯ start Cogny Solo — $9/mo@cogny/cli on npm →
    ❯

    cogny --who

    TWO PATHS
    You're a human

    Today you click through Drip to tag a segment, record a custom event, or check which workflows a subscriber is on. With the CLI you batch-upsert subscribers and apply tags in one scripted call instead of one-by-one in the UI. Connect Drip 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 Drip 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 Drip MCP. Send --input JSON, get JSON back.

    mcp__Drip__list_subscribersList subscribers, filterable by status and tag.
    $ cogny tools call mcp__Drip__list_subscribers \
  --input '{"status":"active","tags":"vip","per_page":2}'
    example response
    {
  "subscribers": [
    {
      "id": "a1b2",
      "email": "ada@example.com",
      "status": "active",
      "tags": [
        "vip",
        "q2-buyer"
      ],
      "lifetime_value": 482
    },
    {
      "id": "c3d4",
      "email": "liu@example.com",
      "status": "active",
      "tags": [
        "vip"
      ],
      "lifetime_value": 119
    }
  ],
  "meta": {
    "page": 1,
    "count": 2,
    "total_count": 318
  }
}
    mcp__Drip__apply_tagApply a tag to a subscriber (creates them if needed).
    $ cogny tools call mcp__Drip__apply_tag \
  --input '{"email":"ada@example.com","tag":"webinar-signup"}'
    example response
    {
  "email": "ada@example.com",
  "tag": "webinar-signup",
  "status": "success"
}
    mcp__Drip__list_campaignsList Email Series campaigns by status.
    $ cogny tools call mcp__Drip__list_campaigns \
  --input '{"status":"active","per_page":2}'
    example response
    {
  "campaigns": [
    {
      "id": "99001",
      "name": "Welcome series",
      "status": "active",
      "email_count": 5,
      "active_subscriber_count": 1204
    },
    {
      "id": "99014",
      "name": "Win-back",
      "status": "active",
      "email_count": 3,
      "active_subscriber_count": 388
    }
  ]
}
    ❯

    cogny tools list

    MORE

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

    mcp__Drip__get_subscribermcp__Drip__upsert_subscribermcp__Drip__batch_subscribersmcp__Drip__record_eventmcp__Drip__list_tagsmcp__Drip__subscribe_to_campaignmcp__Drip__list_workflowsmcp__Drip__start_subscriber_on_workflow
    ❯

    cogny --faq

    Is this an official Drip CLI?

    No — it is the Cogny CLI calling the Drip MCP over the cogny-mcp-proxy. You connect Drip once in Cogny, and then every tool is callable from Bash with your Cogny key — no account id or API token in your shell history.

    Can it record custom events?

    Yes. `record_event` and `batch_record_events` push events into Drip, which is how you trigger event-based workflows. Combine with `apply_tag` and `start_subscriber_on_workflow` to drive automations from a script.

    Can it move subscribers through campaigns and workflows?

    Yes. The MCP exposes `subscribe_to_campaign`, `unsubscribe_from_campaign`, `start_subscriber_on_workflow` and `remove_subscriber_from_workflow`, alongside read tools for campaigns and workflows.

    ❯

    related CLIs

    /cli/mailerlite→/cli/klaviyo→/cli/mailchimp→/cli/brevo→

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