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.

Below is a full breakdown of what is currently available. For prompt examples and use cases in each category, see What you can do with the beehiiv MCP.

• Create and edit post content
• Manage post templates
• Manage content tags

• Create and manage subscriber tags
• Create and manage custom fields
• Create, edit, and manage segments and condition sets
• Create and manage surveys and polls

• Manage signup flows
• Manage subscribe forms and form themes
• View, discover, and manage recommendations

• View ad network opportunities and offers
• View sponsorship agreements
• Manage products and tiers
• View paywalls

• Build and configure automation workflows and emails

• View podcast show and episode data
• Access episode stats and transcripts

• Edit page metadata, including SEO titles and descriptions
• Manage site redirects
• View website analytics and breakdowns

• Upload and manage image assets
• Manage guest authors
• Manage external RSS feeds

Some actions must still be completed in the beehiiv app:

• Publishing or scheduling posts: Drafts can be created and edited via the MCP, but must be published from the app.
• Activating automations: Automation workflows can be built and configured via the MCP, but must be activated in the app.
• Editing website page content: Page metadata (SEO titles, descriptions) is editable, but page body content is not.
• Writing direct sponsorship data or paywall content: These are currently read-only.

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.
   
   
   

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 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 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.

What AI tools does the beehiiv MCP support?
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.
Which plans include access to the beehiiv MCP?
All beehiiv users have access to the beehiiv MCP, with no upgrade required. Your plan determines what you have access to: Write actions — creating, editing, and managing content — require a paid beehiiv plan. Free plans have read-only access to the MCP.
Does my beehiiv plan affect what I can do with the MCP?
Yes. Free plans have read-only access. You can analyze data and generate insights, but cannot create or edit content via the MCP. Write actions, such as creating posts, managing segments, and building automations, require a paid beehiiv plan. To see beehiiv's available plans, visit beehiiv pricing.
What can I do with the beehiiv MCP right now?

You can read and analyze data across your account: content, subscriber data, performance metrics, podcast stats, website analytics, ad opportunities, and more. You can also create and manage posts, post templates, content tags, subscriber tags, custom fields, segments, condition sets, surveys, polls, signup flows, subscribe forms, recommendations, products, tiers, image assets, guest authors, external RSS feeds, and automation workflows.

Some actions, including publishing posts and activating automations, must still be completed from the beehiiv app. See What you can do with the beehiiv MCP for a full breakdown with examples.

Can I create or send content using the beehiiv MCP?
You can create and edit post drafts, post templates, automation emails, and other content types via the MCP. Publishing posts and activating automations must be done from the beehiiv app. Sending posts via the MCP is not currently available.
Will the beehiiv MCP replace the send API for production sends?
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.
New tools were added to the beehiiv MCP but they aren't showing up in my AI client. What should I do?

When beehiiv adds new tools to the MCP, your AI client may not pick them up automatically. To refresh your available tools:

• In Claude: Open the MCP tools dropdown and select Refresh tools list.
• In other AI clients: Disconnect from the beehiiv MCP and reconnect using your MCP settings.

After refreshing, the new tools should be available in your next prompt.

How do workspace user roles and permissions affect MCP access?
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.
Can the beehiiv MCP access payment information?
No. Stripe billing and payment data is not accessible through the beehiiv MCP.
Does the beehiiv MCP use the same permissions as my beehiiv account?
Yes. The beehiiv MCP uses the same workspace user role permissions as your beehiiv account.
What custom fields might be exposed through the MCP?
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.
Am I responsible for how AI tools use my subscriber data?
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.