beehiiv MCP server for your AI

One beehiiv workspace API key. Create it in beehiiv under Settings, then Workspace Settings, then API, with Create New API Key; you need to be a workspace Owner or Admin, and beehiiv shows the key only once. It never expires and needs no OAuth app. PopMCP checks it by listing the publications it reaches, stores it encrypted and sends it from the server as a Bearer token, so your AI client never sees it.

Yes, one per PopMCP workspace. After you paste the key, PopMCP lists every publication it can reach (the whole beehiiv workspace, or only the ones the key is restricted to), and you pick which to connect and the PopMCP workspace each one goes into. Each connection is pinned to its publication, so the AI never passes a publication id and cannot reach one mapped to another workspace. Add more later with Add publications in My MCP.

No, not unless it marks the post confirmed. A post created without a status is published and emailed by beehiiv at once, so PopMCP saves every create_post as a draft unless the AI passes a status, or as confirmed when it sets scheduled_at, which schedules it. The tool description tells the AI to send confirmed only when you asked to publish or schedule. send_post_test_email mails a test to the addresses you name, and creating or updating posts needs a beehiiv Max or Enterprise plan.

Yes. delete_subscription erases the subscriber and all their data and stops billing a premium subscriber, so it is left out of the default tools and the AI is steered to update_subscription with unsubscribe set to true, which can be undone. delete_post archives a sent or scheduled post and only deletes a draft outright. create_data_deletion_request is workspace-wide and redacts the subscriber from every publication after a 14-day delay.

Yes. get_publication with stats expanded returns active free and premium subscriber counts, average open and click rates and total sent. list_posts with stats adds opens and clicks per post, get_posts_aggregate_stats totals them across matching posts with the top 1,000 clicked URLs, and get_engagements breaks email engagement down by day, week or month over up to 31 days. For large publications, beehiiv serves the totals from an hourly cache.

32 in total. 26 are beehiiv webhook events: new, confirmed and deleted subscribers, upgrades to paid and downgrades to free, paused and resumed subscriptions, paid tiers added, removed, paused or resumed, posts sent, scheduled or updated, newsletter list joins, leaves, pauses and resumes, survey responses, and podcast episode and private feed changes. Change detection adds new segments, custom fields, newsletter lists, automations, polls and paid tiers.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 104 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 33-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. Every tool stays searchable, and on Scale the owner can load the full catalog for a teammate's connection.

A tool is something your AI calls, and there are 104 here. A trigger is something PopMCP watches for you: 32 beehiiv events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into beehiiv.