The beehiiv connector.
Newsletter posts, subscribers and stats. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
beehiiv exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
beehiiv defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every beehiiv tool
6 tools, named as the agent sees them.
- list_postsread
List the publication's posts with per-post email and web stats, newest first by default. Rendered HTML is never requested, so results stay small. The `id` returned is the `post_id` that get_post takes.
- get_postread
Get one post with its full email and web stats plus per-link click counts — the tool for "how did this issue perform?". `post_id` comes from list_posts.
- list_subscriptionsread
List subscribers with their status, tier and acquisition source. Contains personal data, so it returns a minimal field set and defaults to 10 — narrow with `status` or `tier` rather than paging the whole list. Use `cursor` from the response to continue.
- get_subscription_by_emailread
Look one subscriber up by email address and see their status, tier, acquisition source and engagement stats. Use this instead of paging list_subscriptions when you already know the address.
- list_segmentsread
List the publication's segments with their size and last-calculated time. Segment stats recalculate roughly daily, so `last_calculated` says how stale `total_results` is.
- get_publication_statsread
Get the publication's headline numbers — active free and premium subscriptions, average open and click rates, totals sent. The one-call answer to "how is the newsletter doing overall?".
Use it from any agent
The same beehiiv tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a beehiiv API Key in your beehiiv account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect beehiiv once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.