cogny cliemailfirst 15 calls free

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

Start free @cogny/cli on npm

01two paths

you're a person

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 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 Drip tool over JSON-RPC. The first 15 calls are free.

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

02tools call

real Drip tools.

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

mcp__Drip__list_subscribers

List 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_tag
Apply 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_campaigns

List 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
    }
  ]
}

03tools list

the rest of the surface.

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

mcp__Drip__get_subscriber
mcp__Drip__upsert_subscriber
mcp__Drip__batch_subscribers
mcp__Drip__record_event
mcp__Drip__list_tags
mcp__Drip__subscribe_to_campaign
mcp__Drip__list_workflows
mcp__Drip__start_subscriber_on_workflow

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

06related

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

drip, then a verdict.

Start free All CLIs