What beehiiv exposes
beehiiv ships an official MCP server, a REST API, and Zapier plus Make integrations, giving me three distinct paths to automate newsletter operations. The MCP server (documented at beehiiv.com/features/mcp) lets Claude, Cursor, and other MCP clients query my publication directly, no glue code required. The REST API at developers.beehiiv.com covers the core objects I work with daily: publications, posts, subscriptions, segments, custom fields, and automations. Zapier and Make handle the no-code side, useful for piping signups in from forms or syncing subscribers to a CRM. Auth method and SDK languages aren't published in the facts I have, so check the developer docs before scoping a build. Webhook availability isn't confirmed here either.
Access, auth, and limits
Getting connected starts at beehiiv.com/mcp, where beehiiv documents the setup for its official server. Authentication runs through OAuth, so you authorize the connection with your beehiiv login rather than copy-pasting an API token, which keeps credentials out of your agent config.
There's no separate hosted URL or Claude Code one-liner in the research I have, so follow beehiiv's own MCP instructions to add it to your client. Because it's a first-party server, plan gating (if any) will follow your beehiiv subscription. The research doesn't list a specific tier requirement, so confirm on their MCP page before assuming free-plan access.
Where it works and what to build
A concrete workflow: ask your agent to 'summarize last week's newsletter open and click rates, then draft three subject line variations for the next issue based on what performed best.' The MCP server pulls the analytics and feeds them straight into the creative step, so you skip the copy-paste loop between dashboard and LLM.
For operations, you could prompt 'check my subscriber growth over the last 30 days and flag any spikes,' or have the agent draft and stage a post directly. beehiiv describes the coverage as creative, analytics, and operations, so treat those three buckets as your playground and test the exact commands against your account.
How to connect beehiiv MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"beehiiv": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://www.beehiiv.com/features/mcp
// Claude Code (one-liner): claude mcp add beehiiv <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: beehiiv.com/features/mcp.
Does beehiiv MCP cost extra?
beehiiv ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your beehiiv plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
beehiiv also publishes a REST API
beehiiv publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with beehiiv from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe beehiiv data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's beehiiv account
- Multi-account workflows without context-switching the beehiiv UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage beehiiv data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production beehiiv safe
Limits and gotchas
- Official MCP server — published by beehiiv themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying beehiiv API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Wiring beehiiv into an agent makes sense if you're a newsletter operator who wants to draft posts, query analytics, and manage sends by prompt instead of clicking through the dashboard. It's official and OAuth-secured, which matters more than most people realize, but the lack of a published endpoint and a documented client list keeps it out of the top tier for now. A solid 7 out of 10.
Moderate agent fit with an official MCP server and documented API, but limited by missing OpenAPI specs and lack of SDK support. The MCP bridge helps with Claude workflows, though you'll need custom auth handling and manual JSON parsing for structured data extraction. Skip this if you need webhooks or native integration with other LLM platforms.
Scored by Joonas (TMB).
beehiiv MCP & API FAQ
Is the beehiiv MCP server official?+
Can I use the beehiiv MCP with Cursor or Codex?+
Does beehiiv have a public API?+
Does beehiiv support webhooks?+
Sources
- beehiiv official site: https://www.beehiiv.com/
- MCP server page: https://www.beehiiv.com/features/mcp
- API docs: https://developers.beehiiv.com
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.