beehiiv

com.beehiivv0.1.0更新於 Oct 7, 2026

Manage beehiiv newsletters, posts, podcasts, community, subscribers, and analytics.

已驗證Streamable HTTP可網頁執行Data & AnalyticsBusiness & CommerceCommunication & Collaboration

概覽

AI 產生的概覽

讓助理透過託管伺服器管理 beehiiv 的電子報、文章、播客、社群、訂閱者、自動化與分析資料。

功能
將 AI 助理連接到 beehiiv 工作區，可起草、編輯與複製文章和範本，讀取文章內容、統計、點擊與留言，並管理社群、成員與邀請。也涵蓋播客、自動化、受眾分群與標籤、變現產品與訂單、成長計畫以及發布分析。search_documentation、read_documentation 等文件工具讓助理取得最新撰寫指引，而不是憑空猜測。
適用情境
適合經營 beehiiv 出版品、希望助理在同一個工作區內準備草稿、檢視成效或處理日常受眾、社群與播客事務的使用者。發布、寄送與啟用自動化仍需在 beehiiv 中由人工完成。
執行需求
需要一個包含 MCP 存取權的 beehiiv 方案帳號，並在工作區中啟用 MCP。伺服器為遠端端點 Streamable HTTP，不在本機執行任何程式。認證採用 OAuth 2.1，透過瀏覽器登入並動態註冊用戶端，用戶端取得 read 與 write 範圍的權杖。部分工具群組受方案與工作區設定限制。
安裝前請注意
用戶端要求 read 與 write 範圍，因此助理可以修改工作區資料，例如文章、成員、角色、邀請、私訊、訂閱、分群與自動化。存取範圍僅限你本人 beehiiv 權限已涵蓋的出版品。發布、寄送與啟用自動化仍由人工在 beehiiv 中操作。若工作區未啟用 MCP，工具呼叫會回傳權限錯誤。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 beehiiv，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "beehiiv": {
      "type": "http",
      "url": "https://mcp.beehiiv.com/mcp"
    }
  }
}

README

beehiiv/agents

Official beehiiv tools for AI agents, built on the beehiiv MCP server.

This repository holds the plugin manifests for Claude Code, Grok Build, Gemini CLI, Cursor and Codex, plus the official MCP registry entry. They all point at the same hosted server at https://mcp.beehiiv.com/mcp. Nothing runs on your machine.

What you can do

Once connected, the agent works against your beehiiv workspace directly:

  • Posts. Draft, edit and duplicate posts and post templates. Read post content, stats, clicks, comments and per-subscriber engagement. Publishing and sending stay human actions in beehiiv, so the agent prepares the post and you press send.
  • Communities. Create channels, publish and pin posts, moderate reports, manage members and roles, send invites and direct messages, read community metrics.
  • Podcasts. Create shows and episodes, upload audio, schedule episodes, read transcripts and episode stats.
  • Automations. Build journeys, steps, triggers and automation emails, including A/B variants. Activating an automation stays a human action in the editor.
  • Audience. Manage subscriptions, segments, tags, custom fields, newsletter lists and signup flows.
  • Monetisation. Products, tiers, premium offers, orders, paywalls, the ad network and the sponsor network.
  • Growth. Recommendations, referral programs, polls and surveys.
  • Analytics. Publication and website analytics, post and podcast stats, poll and survey responses, earnings.

The server also documents itself. Ask the agent to call search_documentation, read_documentation, or any of the learn_* tools, and it fetches current guidance on post authoring and community authoring rather than guessing.

Install

Claude

beehiiv is in the Claude connector directory. Add it from the beehiiv connector page, then sign in when prompted.

ChatGPT

beehiiv is in the shared ChatGPT and Codex plugin directory. Add it from the beehiiv plugin page.

Claude Code and Cursor

/plugin marketplace add beehiiv/agents/plugin install beehiiv@beehiiv

Grok Build

bash
grok plugin install beehiiv/agents

Gemini CLI

bash
gemini extensions install https://github.com/beehiiv/agents

Codex

Run /plugins, select beehiiv, then choose Install Plugin. Codex and ChatGPT share one plugin directory, so installing in either place covers both.

Or add the server to ~/.codex/config.toml by hand:

toml
[mcp_servers.beehiiv]url = "https://mcp.beehiiv.com/mcp"enabled = true

Cloning this repo and trusting it also works. .codex/config.toml registers the server for sessions inside the repo.

Any other MCP client

Point it at https://mcp.beehiiv.com/mcp over Streamable HTTP. Setup snippets are in your beehiiv workspace under Settings → Workspace → MCP.

Authentication

OAuth 2.1. There is no API key to copy and no secret to store in this repo.

On first use your client registers itself automatically (RFC 7591 dynamic client registration) and opens a browser to beehiiv, where you sign in and grant access. The client receives an access token and a refresh token scoped to read and write.

Every tool call is authorised against your own beehiiv permissions. The agent can only reach publications you can already reach.

Requirements

If MCP is off for your workspace, tool calls return a permission error. See Getting started with the beehiiv MCP for the current plan requirements.

Some tool groups are gated separately, so the tools an agent sees depend on your plan and workspace settings.

Layout

.mcp.json lives at plugins/beehiiv/ and states the server URL once.Every ecosystem manifest beside it delegates to that file.
.claude-plugin/marketplace.json     point their client at ./plugins/beehiiv.cursor-plugin/marketplace.json.grok-plugin/marketplace.jsonplugins/beehiiv/.mcp.json           the shared server configplugins/beehiiv/.claude-plugin/     per-ecosystem plugin manifestsplugins/beehiiv/.cursor-plugin/plugins/beehiiv/.grok-plugin/plugins/beehiiv/.codex-plugin/gemini-extension.json               must sit at the repo rootserver.json                         official MCP registry entry

Gemini requires its manifest at the absolute repo root and does not support delegating to a shared file, so the server URL appears there a second time.

Network endpoints and credentials

Declared for review and for anyone auditing what this plugin reaches:

EndpointPurpose
https://mcp.beehiiv.com/mcpThe MCP server. All tool calls.
https://mcp.beehiiv.com/.well-known/oauth-protected-resourceOAuth resource discovery (RFC 9728).
https://mcp.beehiiv.com/.well-known/oauth-authorization-serverOAuth server metadata (RFC 8414).
https://mcp.beehiiv.com/registerDynamic client registration (RFC 7591).
https://mcp.beehiiv.com/authorizeStarts the sign-in flow. Redirects to app.beehiiv.com.
https://mcp.beehiiv.com/tokenToken exchange and refresh.

Credentials required: a beehiiv account. The plugin requests the read and write scopes.

This repository ships no executable code beyond scripts/validate.sh, no install hooks and no local processes. The plugins are JSON manifests pointing at a hosted HTTPS endpoint.

Validate

bash
./scripts/validate.sh

Licence

MIT. See LICENSE.

來源：README.md，提交 0984e4b

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.1.0最新Oct 7, 2026