get a newsletter scriptable from Bash.

real Get a Newsletter tools.

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

• mcp__Get_a_Newsletter__tool_get_report

  Detailed engagement report for one sent newsletter.

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

  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_lists

  List all contact lists with active subscriber counts.

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

  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_contact

  Add 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"}]}'copy

  example response

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

the rest of the surface.

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

• mcp__Get_a_Newsletter__tool_list_contacts
• mcp__Get_a_Newsletter__tool_create_list
• mcp__Get_a_Newsletter__tool_create_draft
• mcp__Get_a_Newsletter__tool_send_draft
• mcp__Get_a_Newsletter__tool_list_senders
• mcp__Get_a_Newsletter__tool_get_report_opens
• mcp__Get_a_Newsletter__tool_get_report_clicks
• mcp__Get_a_Newsletter__tool_get_report_unsubscriptions

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

questions.

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.

• /cli/rule
• /cli/mailerlite
• /cli/mailchimp
• /cli/symplify

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