Beehiiv MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Beehiiv MCP Server?

Beehiiv MCP Server is a Model Context Protocol (MCP) server designed to facilitate interaction with the Beehiiv API v2, enabling Large Language Models (LLMs) to manage Beehiiv publications and posts through standardized tools.

how to use Beehiiv MCP Server?

To use the Beehiiv MCP Server, you need to install the required dependencies, set up your project environment, and configure it with your Beehiiv API credentials. After setup, you can interact with the server through a compatible client like Claude Desktop.

key features of Beehiiv MCP Server?

  • Provides tools for listing publications and posts.
  • Allows retrieval of detailed post information and content.
  • Supports creating new posts on the Beehiiv platform (enterprise only).

use cases of Beehiiv MCP Server?

  1. Automating the management of Beehiiv publications.
  2. Integrating Beehiiv functionalities into AI applications.
  3. Streamlining content creation and publication processes.

FAQ from Beehiiv MCP Server?

  • What are the prerequisites for using the server?

You need Python 3.10 or higher, the uv package manager, a Beehiiv account with API access, and a compatible client like Claude Desktop.

  • Is there a way to troubleshoot if the server doesn't show up?

Yes! Check your configuration file syntax, ensure all paths are absolute, and restart the client.

  • How can I secure my API key?

Never commit your .env file to version control and keep your API key secure.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago