beehiiv Is Live in Cogny: Read Your Newsletter Performance and Draft Posts from an Agent
A lot of companies run their newsletter on beehiiv — the audience is the thing, and the publication, not the company's website, is where the relationship and the revenue live. But until today none of that was reachable from a Cogny agent. Now it is: beehiiv is a live MCP integration in the email catalog alongside MailerLite, Brevo, Get a Newsletter and the rest.
No OAuth dance and no developer app: one API key and one publication id created in beehiiv in about a minute, pasted once into Settings → Cogny Managed MCPs, and your agent is in.
TL;DR
- beehiiv is live now. Connect it with an API key + publication id from your warehouse Settings → Cogny Managed MCPs.
- 17 tools across posts, subscribers, segments and automations. The read tools cover per-post recipients, opens and clicks (plus the aggregate across a publication), subscriptions and lookups, segments with their members, and automations with their journeys.
- Posts are always drafts.
create_postsaves a new post as a draft only — it never schedules or sends to your audience. You publish it in beehiiv when you're ready. - Subscriber and automation writes are confirm-gated.
create_subscription,update_subscription(which can change an email or unsubscribe) andadd_subscription_to_automationdescribe what they would do first and make no call to beehiiv until you approve withconfirm=true.create_subscriptionalso defaults email triggers off (welcome email, reactivation and double opt-in all off unless you ask). - The Email Marketing Optimization scheduled template now recognizes beehiiv alongside the rest of the email catalog.
- Works from any MCP client on
app.cogny.com/mcp. - Included in Solo ($9/mo); bring your own agent and the standard MCP tools run under fair use.
What you can do with it
| Area | What Claude can do |
|---|---|
| Publications | List the publications your API key can access (list_publications) and read one (get_publication) |
| Posts & performance | List posts with their recipients, opens and clicks per post (list_posts), read one post (get_post), and get the aggregate stats across a publication's posts (get_posts_aggregate_stats) |
| Draft posts | Create a new post as a draft (create_post) — never scheduled or sent |
| Subscribers | List subscribers, look one up by email or id, create a new subscriber or re-activate one, and update an existing subscriber — each write asks you to confirm first |
| Segments | List segments, read one, and list the subscribers in a segment |
| Automations | List automations and their journeys, and add a subscriber to an automation — which asks you to confirm first, since it can send emails |
In plain terms: "Which of our last ten posts got the most clicks per recipient?" "How are opens trending across the newsletter this quarter?" "Draft a post announcing next week's launch — don't send it, just save it." "Add the people in the 'engaged last 30 days' segment to the welcome automation, once I confirm." The answers — and the saves — happen against beehiiv's own API, not a spreadsheet.
Writes stay narrow on purpose
The first release is deliberately limited to the safe, reversible moves:
- Drafts only, never sends.
create_postalways saves with a draft status. There is nosend_test_email, and nothing schedules or publishes to your audience. You keep the publish button. - Audience writes are confirm-gated.
create_subscription,update_subscription(which can change an email or unsubscribe a subscriber) andadd_subscription_to_automationfirst describe exactly what they would do — the subscriber email, the automation id or the fields being changed, and that emails may be sent or that the subscriber would be unsubscribed — and make no call to beehiiv until you approve withconfirm=true. Nothing changes without your say-so. - Subscriber triggers default off.
create_subscriptionfires beehiiv's welcome email, double opt-in, reactivation and rerouting only if you pass the fields that turn them on — so nothing is emailed without asking.
There are no delete tools and no segment create/delete or publication update in this release — the agent can look at your automations and segments and act cautiously on subscribers, but it can't tear anything down or change your publication's settings.
Reading is read-only, and honest about it
The read tools are genuinely read-only. Every tool carries MCP behavior annotations, so Cogny's UI and Claude.ai connectors know which ones read and which write. Each post's recipients, opens and clicks come back straight from beehiiv's performance data; the aggregate sums them across the publication. Rate limits are per API key (Free 30 calls/min, Lite 180, Pro 500, Enterprise 800) — on a 429 the integration backs off and retries once, then tells you clearly to wait a minute or raise the plan's allowance.
How to connect it
- In beehiiv, open Settings → API (Workspace Settings) and click Create New API Key. Optionally restrict the key to the publications Cogny should manage. Copy the key — it is only shown once.
- Copy the publication id (pub_...) for the newsletter you want to connect. It's shown in your publication settings, and you can also discover ids later with the
list_publicationstool. - In your warehouse Settings → Cogny Managed MCPs, click Connect on the beehiiv card and paste the API key and publication id.
The credential is stored encrypted and sent only to beehiiv's API. Disconnect any time with one click, and revoke the key back in beehiiv's Settings → API screen if you ever stop using Cogny.
If you publish a newsletter on beehiiv, this is the connector that puts your post performance, subscribers and automations one prompt away — with the safety rail that a draft is a draft until you hit publish. Connect it from your Cogny dashboard and ask your first question.