cogny cliemailfirst 15 calls free

mailerlite from your shell.

List subscribers, groups, segments and campaigns, pull per-campaign subscriber activity, and push new campaigns or group assignments to MailerLite — straight from Bash over the MailerLite MCP. No api_key header to wire, no client library.

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

Start free @cogny/cli on npm

01two paths

you're a person

Today you open the MailerLite dashboard, click into a campaign, and read open/click numbers one report at a time. With the CLI you pull the campaign list and its activity as JSON and diff or chart it however you want. Connect MailerLite 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 MailerLite tool over JSON-RPC. The first 15 calls are free.

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

02tools call

real MailerLite tools.

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

mcp__MailerLite__list_campaigns

List campaigns, optionally filtered by status.

cogny tools call mcp__MailerLite__list_campaigns \ --input '{"limit":3,"filter_status":"sent"}'

example response

{
  "data": [
    {
      "id": "1029",
      "name": "June product update",
      "type": "regular",
      "status": "sent",
      "emails": [
        {
          "subject": "New this month",
          "stats": {
            "sent": 14820,
            "opens_count": 5104,
            "clicks_count": 612
          }
        }
      ]
    },
    {
      "id": "1011",
      "name": "Spring sale",
      "type": "regular",
      "status": "sent",
      "emails": [
        {
          "subject": "20% off everything",
          "stats": {
            "sent": 14110,
            "opens_count": 6230,
            "clicks_count": 1044
          }
        }
      ]
    }
  ]
}

mcp__MailerLite__get_campaign_activity

Per-subscriber open/click activity for one campaign.

cogny tools call mcp__MailerLite__get_campaign_activity \ --input '{"campaign_id":"1029","limit":2}'

example response

{
  "data": [
    {
      "subscriber": {
        "email": "ada@example.com"
      },
      "opened": true,
      "clicked": true,
      "opens_count": 3
    },
    {
      "subscriber": {
        "email": "liu@example.com"
      },
      "opened": true,
      "clicked": false,
      "opens_count": 1
    }
  ],
  "meta": {
    "next_cursor": "eyJpZCI6..."
  }
}

mcp__MailerLite__list_subscribers

List subscribers, filterable by status.

cogny tools call mcp__MailerLite__list_subscribers \ --input '{"limit":2,"filter_status":"active"}'

example response

{
  "data": [
    {
      "id": "770001",
      "email": "ada@example.com",
      "status": "active",
      "opens_count": 41,
      "clicks_count": 9
    },
    {
      "id": "770002",
      "email": "liu@example.com",
      "status": "active",
      "opens_count": 12,
      "clicks_count": 2
    }
  ]
}

03tools list

the rest of the surface.

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

mcp__MailerLite__get_subscriber
mcp__MailerLite__upsert_subscriber
mcp__MailerLite__assign_subscriber_to_group
mcp__MailerLite__list_groups
mcp__MailerLite__create_group
mcp__MailerLite__create_campaign
mcp__MailerLite__schedule_campaign
mcp__MailerLite__list_segments

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 MailerLite CLI?: No — it is the Cogny CLI calling the MailerLite MCP over the cogny-mcp-proxy. You connect MailerLite once in Cogny with a new-generation API token, and then every tool is callable from Bash with your Cogny key.
Does it use the new MailerLite API?: Yes. The proxy targets connect.mailerlite.com — the new-generation API. Legacy "classic" 32-char keys are rejected; generate a new API token in MailerLite and reconnect in Cogny integration settings.
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__MailerLite__list_campaigns --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

mailerlite, then a verdict.

Start free All CLIs