cogny cliemailfirst 15 calls free

rule queried from the terminal.

List subscribers, tags, segments and campaigns, pull per-campaign statistics, tag and update subscribers, and fire transactional sends — from Bash over the Rule MCP. The Rule API without the boilerplate.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Rule toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Rule__tool_get_campaign_statistics --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Today you click into each Rule campaign to read its stats and manage tags one subscriber at a time. With the CLI you pull campaign statistics as JSON and bulk-tag subscribers in a single scripted call. Connect Rule 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 Rule tool over JSON-RPC. The first 15 calls are free.

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

02tools call

real Rule tools.

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

mcp__Rule__tool_get_campaign_statistics
Open/click/bounce stats for one campaign.
- cogny tools call mcp__Rule__tool_get_campaign_statistics \ --input '{"campaign_id":50231}'
example response
```
{
  "campaign_id": 50231,
  "sent": 12040,
  "delivered": 11902,
  "opens": 4810,
  "clicks": 922,
  "bounces": 138,
  "unsubscribes": 34
}
```

mcp__Rule__tool_list_campaigns

List campaigns, optionally filtered by status.

cogny tools call mcp__Rule__tool_list_campaigns \ --input '{"limit":2,"status":"sent"}'

example response

{
  "campaigns": [
    {
      "id": 50231,
      "subject": "June newsletter",
      "status": "sent",
      "message_type": "campaign",
      "sent": 12040
    },
    {
      "id": 50118,
      "subject": "Flash sale",
      "status": "sent",
      "message_type": "campaign",
      "sent": 11540
    }
  ]
}

mcp__Rule__tool_add_subscriber_tags
Add tags to a subscriber.
- cogny tools call mcp__Rule__tool_add_subscriber_tags \ --input '{"identifier":"880142","tags":["vip","q2-buyer"]}'
example response
```
{
  "identifier": "880142",
  "tags": [
    "vip",
    "q2-buyer"
  ],
  "status": "success"
}
```

03tools list

the rest of the surface.

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

mcp__Rule__tool_list_subscribers
mcp__Rule__tool_create_subscriber
mcp__Rule__tool_update_subscriber
mcp__Rule__tool_list_tags
mcp__Rule__tool_list_segments
mcp__Rule__tool_get_campaign
mcp__Rule__tool_schedule_campaign
mcp__Rule__tool_send_transaction

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 Rule CLI?: No — it is the Cogny CLI calling the Rule MCP over the cogny-mcp-proxy. You connect Rule once in Cogny with your API token, and then every tool is callable from Bash with your Cogny key.
Can it send transactional email?: Yes. `tool_send_transaction` fires a transactional send, alongside campaign tools (list, get, schedule, send) and subscriber/tag management. It is the same Rule API surface, scriptable.
Can my coding agent use this without MCP setup?: Yes — that is the point. `npx @cogny/cli init --agent claude-code` issues a key, then `cogny tools call mcp__Rule__tool_get_campaign_statistics --input ...` works 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

rule, then a verdict.

Start free All CLIs