Beehiiv MCP server for AI agents

Live

BEARER TOKEN

NEWSLETTERS

Communication

Beehiiv gives your agent newsletter operations across your publications: draft and schedule posts, manage subscribers, tags, and segments, enroll readers in automations, and read engagement and post stats.

  • Per-user credentials: each call uses the actual user's access token, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
Beehiiv
agent · Acme Q3
Run
How did last week's issue perform on opens and clicks?
S
beehiiv_get_post
112ms
Newsletter agent
The October 16 issue went to 18,400 subscribers with a 52% open rate and 2,310 clicks. The pricing link drew the most clicks.
Sources: 1 post, email and click stats
beehiiv
1 post
18:29
Message Claude...

Tools your newsletter agent reaches for on Beehiiv, scoped per user.

CALL ANY TOOL
60 tools for newsletters in Beehiiv: create and schedule posts, add and update subscribers, tag and segment readers, enroll them in automations, run exports, and read engagement and post stats.
beehiiv_add_subscription_tags
Add subscription tags
Add one or more tags to a subscriber. Returns the updated subscription. Use this to label subscribers for segmentation. Use beehiiv_update_subscription_by_id for other subscriber changes. Requires a subscription_id from beehiiv_list_subscriptions.
Parameters
Name
Type
Required
Description
publication_id
string
Required
The ID of the beehiiv publication this request applies to. Starts with pub_. Use beehiiv_list_publications to find IDs. Example: pub_00000000-0000-0000-0000-000000000000.
subscription_id
string
Required
The ID of the subscription. Starts with sub_. Use beehiiv_list_subscriptions to find IDs. Example: sub_00000000-0000-0000-0000-000000000000.
tags
array
Optional
Tags that can be used to group subscribers. Example: ["vip","customer"].
beehiiv_add_subscription_to_newsletter_list
List add subscription to newsletter
beehiiv_bulk_create_subscriptions
Bulk create subscriptions
beehiiv_create_post
Post create
beehiiv_create_subscription_export
Export create subscription
beehiiv_delete_custom_field
Delete custom field
beehiiv_delete_newsletter_list
List delete newsletter
beehiiv_delete_post
Post delete
beehiiv_delete_segment
Delete segment
beehiiv_get_author
Get author
beehiiv_get_automation_journey
Get automation journey
beehiiv_get_custom_field
Get custom field
beehiiv_get_poll
Get poll
beehiiv_get_post_aggregate_stats
Get post aggregate stats
beehiiv_get_publication
Get publication
beehiiv_get_segment
Get segment
beehiiv_get_subscription_by_id
Get subscription by id
beehiiv_identify_workspace
Identify workspace
beehiiv_list_authors
List authors
beehiiv_list_automation_journeys
List automation journeys
beehiiv_list_condition_sets
List condition sets
beehiiv_list_newsletter_list_subscriptions
List newsletter list subscriptions
beehiiv_list_poll_responses
List poll responses
beehiiv_list_post_templates
List post templates
beehiiv_list_publications
List publications
beehiiv_list_segment_subscriber_ids
List segment subscriber ids
beehiiv_list_subscription_exports
List subscription exports
beehiiv_list_tiers
List tiers
beehiiv_update_custom_field
Update custom field
beehiiv_update_subscription_by_id
Update subscription by id

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Beehiiv tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["beehiiv"], toolNames: [
    "beehiiv_list_posts",
    "beehiiv_get_post",
    "beehiiv_create_post"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Summarize last week's newsletter stats and draft next week's issue" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["beehiiv"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Summarize last week's newsletter stats and draft next week's issue" }],
  tools,
});

// Execute the tool call with the user's vaulted Beehiiv access token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["beehiiv"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Summarize last week's newsletter stats and draft next week's issue" }],
  tools,
});

// Tool call runs with the user's vaulted Beehiiv access token
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["beehiiv"] }, pageSize: 100,
});

const agent = new Agent({
  name: "newsletter_agent",
  model: "gemini-2.5-pro",
  instruction: "Beehiiv tools scoped to this user",
  tools,
});

await agent.run("Summarize last week's newsletter stats and draft next week's issue");
Try these prompts
Copy any prompt into your agent. Each maps directly to a Beehiiv tool. Click to copy, paste into your agent, done.
Posts
Copy the prompt
Copied
Draft a post titled Weekly Product Notes and schedule it for Friday at 8am.
Copy the prompt
Copied
List the posts we published in the last 30 days.
Copy the prompt
Copied
Show the open and click stats for our most recent issue.
Subscribers
Copy the prompt
Copied
Subscribe jane@acme.com to our publication with the tag webinar.
Copy the prompt
Copied
Look up the subscriber alex@globex.com and show their status and tier.
Copy the prompt
Copied
Start an export of every subscriber in the Active Readers segment.
Automations and segments
Copy the prompt
Copied
List the automations in our publication and their status.
Copy the prompt
Copied
Enroll sam@initech.com in the Welcome Series automation.
Copy the prompt
Copied
Recalculate the Engaged 90 Days segment and list its members.
SEE HOW AUTH WORKS
Each user connects their own Beehiiv access token once, and Scalekit sends it with every call. Access tokens stay vaulted, every call is scope checked, and every action is logged.
1
Authorize
Your user connects
Beehiiv
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Beehiiv
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Beehiiv
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Beehiiv
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other marketing and email connectors.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
GTM and RevOps Teams
Outbound prospecting agent
Searches Apollo for prospects matching your ICP, scores and ranks them, drafts personalized outreach in Gmail, and logs every send to Google Sheets. Mail goes out as the rep, not from a shared inbox.
Test other agents
See the same per-user auth pattern across other marketing and email connectors.
GTM
Competitive intelligence briefing agent
Scan Gong calls for competitor mentions, match each one to its Notion battlecard, and DM every affected rep a single Slack digest.
SALES
Outbound prospecting agent
Search Apollo for ICP matches, rank them, draft personalised Gmail outreach, and log every send to Google Sheets.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared Beehiiv access token looks fine in a demo. In production every post and subscriber change looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Beehiiv today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Beehiiv as the user or through a shared access token?
As the user. Each user connects their own Beehiiv access token once, and Scalekit sends it with every call. Audit logs attribute every post and subscriber change to that user, not a shared service account.
Where is the Beehiiv access token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new access token. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.
Can I limit what the agent does in Beehiiv?
Yes. Filter by tool name in listScopedTools to expose only what you want, for example the post and stats tools without beehiiv_delete_subscription, which permanently removes a subscriber. Scalekit also enforces scope checks before every API call.
What happens when a user revokes Beehiiv access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Which Beehiiv publications can the agent work with?
Every publication the user's access token can reach. beehiiv_list_publications returns them, and each post, subscriber, segment, and automation tool takes a publication id, so one agent can work across several newsletters.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""beehiiv"": {
""url"": ""https://mcp.scalekit.com/beehiiv"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.beehiiv]
url = ""https://mcp.scalekit.com/beehiiv""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""beehiiv"": {
""url"": ""https://mcp.scalekit.com/beehiiv"",
""type"": ""http""
}
}
}