Beehiiv

What the beehiiv MCP server does

The beehiiv MCP server gives AI clients access to a beehiiv workspace through the hosted endpoint at https://mcp.beehiiv.com/mcp. It covers newsletter posts and templates, community activity, podcasts, automations, subscriber data, monetization, growth programs, and analytics.

Agents can draft, edit, duplicate, and inspect posts, including content, clicks, comments, statistics, and subscriber-level engagement. Community operations include channels, posts, reports, members, roles, invitations, direct messages, and metrics. Podcast capabilities include shows, episodes, audio uploads, scheduling, transcripts, and episode statistics.

The server also supports journeys and automation emails, audience subscriptions and segmentation, products and premium offers, recommendations and referrals, polls and surveys, and publication or website reporting. Documentation tools such as search_documentation, read_documentation, and learn_* provide current guidance for supported authoring workflows.

How it works

The beehiiv MCP server is hosted remotely; cloning the repository is not required, and the repository contains configuration manifests rather than a local server process. MCP clients connect over Streamable HTTP and send tool calls to the hosted endpoint.

Authentication uses OAuth 2.1 with dynamic client registration. On first connection, the client opens beehiiv in a browser for sign-in and consent, then receives access and refresh tokens with read and write scopes. Each request is checked against the signed-in user’s beehiiv permissions, so the agent can access only publications that user can already reach.

Publishing or sending a post remains a human action in beehiiv. Activating an automation also stays in the beehiiv editor rather than being performed automatically by the agent.

Setup and configuration

The workspace must have MCP enabled, and the beehiiv account must use a plan that includes MCP access. Workspace administrators can check this under Settings → Workspace → MCP. Available tool groups may vary by plan and workspace configuration.

Supported installation paths include the Claude connector, the shared ChatGPT and Codex plugin directory, Claude Code, Cursor, Grok Build, and Gemini CLI. Other MCP clients can use the hosted URL directly. Codex can also register the server in ~/.codex/config.toml with the URL and an enabled flag.

No API key or repository secret is needed. The repository documents OAuth discovery, registration, authorization, and token endpoints, but credentials consist of the user’s beehiiv account and the OAuth grant.

Tools and capabilities

• Prepare, edit, duplicate, and inspect newsletter posts and templates.
• Manage community channels, members, roles, moderation reports, posts, invites, and messages.
• Create and schedule podcast shows and episodes, upload audio, and read transcripts and statistics.
• Build automation journeys, triggers, steps, emails, and A/B variants.
• Manage subscriptions, segments, tags, custom fields, lists, and signup flows.
• Work with products, tiers, offers, orders, paywalls, and sponsor or ad network data.
• Review analytics, poll and survey responses, earnings, referrals, and recommendations.

Limitations and notes

Tool availability depends on the beehiiv plan and workspace settings. If MCP is disabled, calls return a permission error. Access is limited by the authenticated user’s existing beehiiv permissions.

The beehiiv MCP server prepares content and performs supported workspace operations, but sending posts and activating automations require a person to complete those actions in beehiiv. The repository includes a validation script, but it does not install a local runtime or start a local service. It is licensed under MIT.