Beehiiv MCP integration for AI agents.
Connect AI agents to Beehiiv through 6 structured actions, including get post, get publication, and get subscription. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Beehiiv integration exposes
The Beehiiv Agent App exposes 6 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent fetch one beehiiv post by id with optional statistics or content expansion, fetch one beehiiv publication by id with optional statistics expansion, and fetch one beehiiv subscription by id with optional expansions. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Beehiiv account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Beehiiv capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_postREADFetch one Beehiiv post by ID with optional statistics or content expansion.
INPUTS: publicationId / postId / expand / premiumTiers
get_publicationREADFetch one Beehiiv publication by ID with optional statistics expansion.
INPUTS: publicationId / expand
get_subscriptionREADFetch one Beehiiv subscription by ID with optional expansions.
INPUTS: publicationId / subscriptionId / expand
list_postsREADList Beehiiv posts for a publication with documented filters and optional expansions.
INPUTS: publicationId / expand / audience / platform / status
list_publicationsREADList Beehiiv publications associated with the API key, with optional sorting and expansion.
INPUTS: expand / limit / page / direction / orderBy
list_subscriptionsREADList Beehiiv subscriptions for a publication with cursor pagination and documented filters.
INPUTS: publicationId / expand / status / tier / premiumTiers
INPUT CONTRACTS
Know what the action needs before it runs.
get_post
publicationIdREQUIRED- Beehiiv publication ID that owns the post.
postIdREQUIRED- Beehiiv post ID to retrieve.
expandOPTIONAL- Post fields to expand in the Beehiiv response. HTML content expansions can make responses large.
premiumTiersOPTIONAL- Premium tier display names used to scope expanded post content.
get_publication
publicationIdREQUIRED- Beehiiv publication ID to retrieve.
expandOPTIONAL- Publication fields to expand in the Beehiiv response.
get_subscription
publicationIdREQUIRED- Beehiiv publication ID that owns the subscription.
subscriptionIdREQUIRED- Beehiiv subscription ID to retrieve.
expandOPTIONAL- Subscription fields to expand in the Beehiiv response.
list_posts
publicationIdREQUIRED- Beehiiv publication ID whose posts should be listed.
expandOPTIONAL- Post fields to expand in the Beehiiv response. HTML content expansions can make responses large.
audienceOPTIONAL- Audience filter for returned posts.
platformOPTIONAL- Platform filter for returned posts.
statusOPTIONAL- Status filter for returned posts.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Post
Fetch one Beehiiv post by ID with optional statistics or content expansion. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_postVerify with Get Publication
Fetch one Beehiiv publication by ID with optional statistics expansion. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_publicationSAFETY BOUNDARY
Operate Beehiiv with explicit limits
- Authorize Beehiiv with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Beehiiv data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Beehiiv rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Beehiiv task completed successfully.
CONNECTION MODEL
API key
Beehiiv API key used as a bearer token. Create it from Settings > Integrations > API in your Beehiiv account: https://developers.beehiiv.com/welcome/create-an-api-key.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Beehiiv.