Cogny CLI · Email

    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 15 calls) — uses your git email
$ npx @cogny/cli init --agent claude-code

# 2. see every MailerLite tool
$ cogny tools list

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

    cogny --who

    TWO PATHS
    You're a human

    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 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 MailerLite 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 MailerLite MCP. Send --input JSON, get JSON back.

    mcp__MailerLite__list_campaignsList 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_activityPer-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_subscribersList 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
    }
  ]
}
    ❯

    cogny tools list

    MORE

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

    mcp__MailerLite__get_subscribermcp__MailerLite__upsert_subscribermcp__MailerLite__assign_subscriber_to_groupmcp__MailerLite__list_groupsmcp__MailerLite__create_groupmcp__MailerLite__create_campaignmcp__MailerLite__schedule_campaignmcp__MailerLite__list_segments
    ❯

    cogny --faq

    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.

    ❯

    related CLIs

    /cli/mailchimp→/cli/klaviyo→/cli/brevo→/cli/drip→

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