Updated: 2026-04-30 15:21:46 UTC

Getting started with the beehiiv MCP

The beehiiv MCP (Model Context Protocol) server allows you to connect your beehiiv account to any AI tool that supports the Model Context Protocol, including Claude, Claude Code, Cursor, and Codex. The beehiiv MCP is available to all beehiiv users with no waitlist or paid plan required.

Once connected, your AI tool can securely access your entire beehiiv ecosystem, including content, subscriber information, performance metrics, podcasts, automations, products, surveys, polls, and referrals, and use it to generate insights and complete tasks on your behalf.

This article covers what you can do with the beehiiv MCP, how to connect it to your AI tool of choice, ways it differs from the beehiiv API, and answers to frequently asked questions.

What you can do with the beehiiv MCP

Once connected, you can prompt your AI tool to perform tasks using your real beehiiv data. 
Examples include:

  • Analyze subject line performance across your recent posts.
  • Identify subscriber segments with high unsubscribe rates.
  • Find out which podcast episodes are getting the most plays, from which apps, and in which cities.
  • Identify where subscribers are dropping off from an onboarding automation.
  • Audit your beehiiv website for SEO improvements.

Creating segments

Subscriber segments can be created using a plain-language prompt. 
Examples include:

  • Find my free subscribers who've opened 5+ emails in the last 30 days but haven't upgraded, then save them as a segment called ‘High Intent Free’ in my account. 
  • Build a segment of paid subscribers who've clicked 3+ sponsor links this quarter.

How to connect your AI to the beehiiv MCP

In order to connect the beehiiv MCP, you will need an active account with your AI tool of choice. Setup guides are available in-app for Claude, Claude Code, Cursor, and Codex.

  1. Click Settings at the bottom of the left corner of your account. 
  2. From the left panel, click MCP.

  3. Select your AI client. Setup guides are available for Claude, Claude Code, Cursor, Codex, and Other tools that support the Model Context Protocol.
  4. Follow the on-screen instructions to grant access and connect your account.

Data accessible via the beehiiv MCP is determined by your workspace user role and permissions. You will only be able to access data that is available to you in-app based on your current permission set.

MCP vs. API: Which should you use?

The beehiiv MCP and the beehiiv API are separate surfaces with different design philosophies. The right choice depends on what you are building and how much you need the interface to stay consistent over time.

The beehiiv API

The beehiiv API is built for developer-style integrations. It is versioned with a long-lived contract, meaning beehiiv will not introduce breaking changes or deprecations without advance notice, typically following a new version release. If you need a stable, predictable interface that will not change unexpectedly, the API is the right choice.

Best used for: Programmatic integrations where a consistent, reliable interface is a priority.

The beehiiv MCP

The beehiiv MCP is built for AI agents, which are non-deterministic by nature and designed to adapt. There is no fixed version — beehiiv continuously improves MCP tools to better serve the agent use case, so response formats and behaviors may change over time. If you want to do something through an AI agent that can adapt to those changes, the MCP is the right choice.

Best used for: Building workflows inside AI tools where flexibility and adaptability matter more than a fixed interface.

Frequently asked questions about the beehiiv MCP

  1. The beehiiv MCP provides setup guides for Claude, Claude Code, Cursor, and Codex. Any other AI tool that supports a remote hosted MCP server can also be connected using the Other option in your MCP settings.
  2. All beehiiv users have access to the beehiiv MCP. No upgrade is required.
  3. You can ask your AI tool to analyze your content, subscriber data, and performance metrics and generate insights based on that data. You can also create subscriber segments using plain-language prompts. Revenue and ad performance reporting is not yet available but is coming soon. Additional write functionality is also in development.
  4. Segment creation is currently available as a write-enabled action. Additional write functionality is in development.
  5. No. As additional MCP write functionality becomes available, there will be some overlap with send API capabilities. However, if consistency and reliability in formatting and design are a priority, the beehiiv API will remain the better choice for production sends.
  6. All workspace user roles can use the beehiiv MCP. However, the data accessible to each user via the MCP is limited to what that user can view in-app based on their workspace role and permissions.
  7. No. Stripe billing and payment data is not accessible through the beehiiv MCP.
  8. Yes. The beehiiv MCP uses the same workspace user role permissions as your beehiiv account.
  9. Any custom fields you've configured in your subscribe forms — such as name, company, or other subscriber-provided details — may be accessible via the MCP. To see exactly what data you've collected, go to Subscribers > Custom fields.
  10. Yes. You are responsible for ensuring that any third-party tools you connect to your beehiiv workspace comply with applicable privacy laws and your own privacy commitments to subscribers.