Cogny CLI · Email

Get a Newsletter scriptable from Bash.

Manage contacts, lists, drafts and senders, send or schedule newsletters, and pull detailed delivery reports — opens, clicks, bounces and unsubscriptions — from the shell over the Get a Newsletter MCP. No REST client to build.

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

# 2. see every Get a Newsletter tool
$ cogny tools list

# 3. call any tool from Bash — no MCP wiring
$ cogny tools call mcp__Get_a_Newsletter__tool_get_report --input '{…}'

❯ start Cogny Solo — $9/mo@cogny/cli on npm →

❯

cogny --who

TWO PATHS

You're a human

Today you log into Get a Newsletter, open a sent newsletter, and read its report tab by tab. With the CLI you pull the report and its open/click breakdowns as JSON in one call you can pipe into a spreadsheet or an agent. Connect Get a Newsletter 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 Get a Newsletter 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 Get a Newsletter MCP. Send --input JSON, get JSON back.

mcp__Get_a_Newsletter__tool_get_reportDetailed engagement report for one sent newsletter.

$ cogny tools call mcp__Get_a_Newsletter__tool_get_report \
  --input '{"report_id":"48213"}'

example response

{
  "report_id": "48213",
  "subject": "Weekly digest #34",
  "sent": 8420,
  "delivered": 8312,
  "opens": 3104,
  "clicks": 488,
  "bounces": 108,
  "unsubscriptions": 21
}

mcp__Get_a_Newsletter__tool_list_listsList all contact lists with active subscriber counts.

$ cogny tools call mcp__Get_a_Newsletter__tool_list_lists \
  --input '{"page":1}'

example response

{
  "count": 2,
  "results": [
    {
      "hash": "a1b2c3",
      "name": "Newsletter",
      "active_subscribers": 8420
    },
    {
      "hash": "d4e5f6",
      "name": "Product updates",
      "active_subscribers": 2110
    }
  ]
}

mcp__Get_a_Newsletter__tool_create_contactAdd a contact and subscribe it to one or more lists.

$ cogny tools call mcp__Get_a_Newsletter__tool_create_contact \
  --input '{"email":"ada@example.com","first_name":"Ada","lists":[{"hash":"a1b2c3"}]}'

example response

{
  "email": "ada@example.com",
  "first_name": "Ada",
  "active": 1,
  "lists": [
    {
      "hash": "a1b2c3",
      "name": "Newsletter"
    }
  ]
}

❯

cogny tools list

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

mcp__Get_a_Newsletter__tool_list_contactsmcp__Get_a_Newsletter__tool_create_listmcp__Get_a_Newsletter__tool_create_draftmcp__Get_a_Newsletter__tool_send_draftmcp__Get_a_Newsletter__tool_list_sendersmcp__Get_a_Newsletter__tool_get_report_opensmcp__Get_a_Newsletter__tool_get_report_clicksmcp__Get_a_Newsletter__tool_get_report_unsubscriptions

❯

cogny --faq

Is this an official Get a Newsletter CLI?

No — it is the Cogny CLI calling the Get a Newsletter MCP over the cogny-mcp-proxy. You connect Get a Newsletter once in Cogny, and then every tool is callable from Bash with your Cogny key.

Can it send newsletters or only read reports?

Both. The MCP exposes read tools (contacts, lists, reports, opens/clicks/bounces) and write tools (create and send drafts, schedule sends, manage senders and attributes).

How are reports structured?

Each sent newsletter has a report id. `tool_get_report` gives the summary; `tool_get_report_opens`, `tool_get_report_clicks`, `tool_get_report_bounces` and `tool_get_report_unsubscriptions` give the per-recipient breakdowns as JSON.

❯

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

Get a Newsletter scriptable from Bash.

cogny --who

cogny tools call

cogny tools list

cogny --faq

related CLIs