Is this an official beehiiv MCP server?

No. It is Memtro's MCP server with Memtro's beehiiv connector behind it: the connector reads beehiiv through its API with the credentials you connect on Dashboard → Connections, and beehiiv publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in beehiiv?

Only when you ask, and only what it has been granted: draft a newsletter post; edit a draft or scheduled post's title, subtitle, content, tags or send time; send a test copy of a post to named addresses; publish a draft post to the audience now, or schedule it; delete a draft post, or archive a published one; subscribe an email address, optionally with a welcome email; change a subscriber's email, custom fields or lists, or unsubscribe them; delete a subscriber and all their data (permanent); add a subscriber to an automation, which sends them its emails; delete a segment (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Marketing automation

beehiiv MCP server

beehiiv in any MCP client, through Memtro: beehiiv does not publish this server. Memtro's beehiiv connector reads beehiiv through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

beehiiv newsletters: the publication and its subscriber totals and average rates, posts with email opens, clicks and web views, a post's text, subscriptions by email or status with engagement, segments, automations and newsletter lists; can also draft, edit, test-send, publish or schedule and delete posts, subscribe, update, unsubscribe or delete subscribers, add a subscriber to an automation and delete a segment when you ask (beehiiv allows 30 requests a minute on Free, 180 on Lite, 500 on Pro and 800 on Enterprise.).

Reads

beehiiv_publicationThe connected beehiiv publication: name, organisation, when created, and its totals — active subscriptions (free and premium)…
beehiiv_postsBeehiiv posts, newest first: title, status (draft, confirmed = published or scheduled, archived), platform (email, web, both), audience…
beehiiv_postOne beehiiv post by id with its text (the web version for free readers, HTML stripped and cut to max_chars), full email and web stats…
beehiiv_subscriptionsBeehiiv subscriptions: by exact email (one record, with engagement stats, tags and custom fields), or a list filtered by status (active, inactive…
beehiiv_segmentsSegments of the beehiiv audience: id, name, type (dynamic, static, manual), status…
beehiiv_automationsBeehiiv automations (id, name, status, what triggers them) and newsletter lists (id, name, status, subscriber count).

Acts, when you ask

These change something in beehiiv. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

beehiiv_create_postDrafts a newsletter post in beehiiv from a title and HTML body.
beehiiv_update_postEdits a beehiiv post that has not been sent: title, subtitle, HTML content (replaces it), content tags (replace them) or, for a scheduled post…
beehiiv_send_test_emailSends a test copy of a beehiiv post to the addresses given (at most 5), and nobody else; beehiiv caps test sends per day.
beehiiv_publish_postPublishes a draft beehiiv post to its audience, emailing every subscriber it is set to reach (people outside the company) and putting it on the web…
beehiiv_delete_postDeletes a beehiiv post: a draft is deleted permanently, and a published or scheduled post is archived (taken off the web…
beehiiv_create_subscriptionSubscribes an email address to the beehiiv publication.
beehiiv_update_subscriptionChanges a beehiiv subscriber found by their email: a new email address, custom field values, newsletter lists joined or left…
beehiiv_delete_subscriptionDeletes a beehiiv subscriber and every piece of data held on them, permanently; a premium subscriber stops being billed.
beehiiv_add_to_automationAdds an existing beehiiv subscriber, by email or sub_ id, to an automation, which then sends them its emails on its schedule.
beehiiv_delete_segmentDeletes a beehiiv segment permanently; the subscribers in it are not affected.

Connect it

First connect beehiiv on Dashboard → Connections, then add Memtro to your client once. The beehiiv tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared beehiiv connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How did last Thursday's post do compared with the four before it?
› Which links did readers click most in the 'October roundup' post?
› Is priya@marlowe.studio subscribed, and does she open our emails?
› How many premium subscribers do we have and what is our average open rate?
› Draft a post titled 'November roundup' from these notes and send me a test

Questions

Is this an official beehiiv MCP server?: No. It is Memtro's MCP server with Memtro's beehiiv connector behind it: the connector reads beehiiv through its API with the credentials you connect on Dashboard → Connections, and beehiiv publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in beehiiv?: Only when you ask, and only what it has been granted: draft a newsletter post; edit a draft or scheduled post's title, subtitle, content, tags or send time; send a test copy of a post to named addresses; publish a draft post to the audience now, or schedule it; delete a draft post, or archive a published one; subscribe an email address, optionally with a welcome email; change a subscriber's email, custom fields or lists, or unsubscribe them; delete a subscriber and all their data (permanent); add a subscriber to an automation, which sends them its emails; delete a segment (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.