# beehiiv MCP connector

Connect beehiiv to Elaichi and Claude, ChatGPT, Cursor or any MCP client can read and edit your posts, subscribers, segments, automations and podcast episodes, with each person signed in as themselves and every call logged.

Source: https://elaichi.ai/connectors/beehiiv/

## Facts

| | |
| --- | --- |
| Application | beehiiv |
| Category | Marketing Automation |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. beehiiv builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | www.beehiiv.com/support |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once beehiiv is connected

- Which segments grew the most this week?
- Draft a post from these notes about the pricing change
- Show open rates for last month's sponsored posts

## Connect beehiiv in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick beehiiv.
2. Optionally set Share with, then press Connect.
3. Approve it in beehiiv. beehiiv's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which beehiiv tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## beehiiv MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## beehiiv MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## beehiiv MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect beehiiv to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a beehiiv tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with beehiiv through Elaichi

### Draft next week's post from a brief

Editorial. Turn a page of notes into a post draft in beehiiv, then open it in the beehiiv app to polish and publish.

### See which segments grew this week

Growth. Ask how subscriber counts moved by segment since Monday and which signup sources brought the new readers in.

### Build a segment for the launch campaign

Marketing. Set up a beehiiv segment of readers who opened the last three issues, ready for the automation that follows.

### Fix a reader's record after a reply

Support. Look up a subscriber by email, update their status or tags, and check which automations they are sitting in.

### Pull numbers for a sponsor call

Sales. Get opens and clicks on the last sponsored posts before the call, without digging through the beehiiv dashboard.

### Get a weekly publication summary

Leadership. Ask for subscriber growth, open rates, top posts and podcast episodes across every publication, summarized in one place.

## Elaichi vs Zapier MCP vs Composio for beehiiv

All three can connect beehiiv to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over beehiiv tools | Allow or restrict single beehiiv tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per beehiiv call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect beehiiv to Claude?

Connect beehiiv in Elaichi first: click connect, sign in to beehiiv in the window that opens, and approve the access. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no client ID or secret to generate for beehiiv, and no OAuth application to register.

### Does beehiiv work with ChatGPT and Cursor as well as Claude?

Yes. Once beehiiv is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect beehiiv once and every client uses it.

### What can an AI agent actually do with my beehiiv data?

It can read and edit your beehiiv posts, subscribers, segments, automations and podcast episodes, and pull analytics such as opens and clicks. You can ask it to draft a post, find a subscriber, build a segment or report on last month's issues. Publishing still happens in the beehiiv app, and short concrete asks work better than long sentences.

### Does connecting beehiiv give the AI every publication and subscriber list?

No. Access follows the person who signed in to beehiiv, so someone who can see one publication only gets that publication's posts and subscribers through the AI. Elaichi can narrow that access further for a team, and it never widens it beyond what beehiiv already allows.

### Can my team share one beehiiv connection?

Yes. One person connects beehiiv in Elaichi and shares the connection with a team, and nobody else handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every beehiiv call.

### Can I stop an agent from deleting or changing things in beehiiv?

Yes. Restrictions in Elaichi work per action, so you can allow reading beehiiv posts and subscribers while blocking edits or deletions. A restricted action is never advertised to the AI client, so no prompt can reach it.

### What happens to a beehiiv connection when someone leaves?

Offboarding a person in Elaichi ends their access to beehiiv through every client at once. A beehiiv connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting beehiiv once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the beehiiv MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. beehiiv is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for beehiiv?

Yes. Both let Claude, ChatGPT or Cursor use beehiiv. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every beehiiv call.

### How is Elaichi different from Composio for beehiiv?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to beehiiv: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.