cogny cliemailfirst 15 calls free
mailchimp scriptable from the shell.
List audiences, members, segments, campaigns and automations, pull open/click reports, and create or send campaigns in Mailchimp — from Bash over the Mailchimp MCP. The Marketing API without wrangling the data-center prefix on every request.
- 1. sign up, free for the first calls (uses your git email)
npx @cogny/cli init --agent claude-code - 2. see every Mailchimp tool
cogny tools list - 3. call any tool from bash, no MCP wiring
cogny tools call mcp__Mailchimp__tool_get_report --input '{…}'
Reading Mailchimp campaign reports or syncing a segment means clicking through the dashboard tab by tab. The CLI returns reports and member lists as JSON, and lets you add members or send a campaign in one scriptable call. Connect Mailchimp once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.
Start SoloSign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Mailchimp tool over JSON-RPC. The first 15 calls are free.
npx @cogny/cli init --agent claude-code
real Mailchimp tools.
Tool names as the Mailchimp MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.
- mcp__Mailchimp__tool_get_report
Open/click/bounce report for a sent campaign.
cogny tools call mcp__Mailchimp__tool_get_report \ --input '{"campaign_id":"abc123def"}'
example response
{ "id": "abc123def", "emails_sent": 18422, "opens": { "open_rate": 0.41, "unique_opens": 7553 }, "clicks": { "click_rate": 0.067, "unique_clicks": 1234 }, "bounces": { "hard_bounces": 21, "soft_bounces": 44 } } - mcp__Mailchimp__tool_list_audiences
List audiences (lists) with member counts.
cogny tools call mcp__Mailchimp__tool_list_audiences \ --input '{"count":2}'
example response
{ "lists": [ { "id": "a1b2c3", "name": "Newsletter", "stats": { "member_count": 28410 } }, { "id": "d4e5f6", "name": "Customers", "stats": { "member_count": 9120 } } ] } - mcp__Mailchimp__tool_add_member
Add a subscriber to an audience.
cogny tools call mcp__Mailchimp__tool_add_member \ --input '{"list_id":"a1b2c3","email_address":"jane@example.com","status":"subscribed","merge_fields":{"FNAME":"Jane"}}'
example response
{ "id": "f1e2d3", "email_address": "jane@example.com", "status": "subscribed", "list_id": "a1b2c3" }
the rest of the surface.
A sample of the other Mailchimp tools. Run cogny tools list --json for every tool and its input schema.
- mcp__Mailchimp__tool_get_account_info
- mcp__Mailchimp__tool_list_campaigns
- mcp__Mailchimp__tool_create_campaign
- mcp__Mailchimp__tool_send_campaign
- mcp__Mailchimp__tool_list_members
- mcp__Mailchimp__tool_list_segments
- mcp__Mailchimp__tool_create_segment
- mcp__Mailchimp__tool_list_automations
- mcp__Mailchimp__tool_get_report_click_details
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.
questions.
- Is this an official Mailchimp CLI?
- No — it is the Cogny CLI calling the Mailchimp MCP over the cogny-mcp-proxy. You connect your Mailchimp API key once inside Cogny; the proxy handles the data-center prefix and auth for you.
- Can it send campaigns or just report?
- Both. The Mailchimp MCP exposes read tools (campaigns, reports, audiences, members, segments) and write tools (create/update/send campaigns, add members, build segments).
- Can my coding agent use this without MCP setup?
- Yes. `npx @cogny/cli init` issues a key, then `cogny tools call mcp__Mailchimp__tool_get_report --input ...` works from any shell — no /mcp wiring or restart needed.
Building an agent? The full tool map for every server is one fetch: /cli/llms.txt