Beehiiv Newsletter Subscription MCP Server using FastMCP.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-server-beehiiv","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Beehiiv Newsletter MCP Server This is a Model Context Protocol (MCP) server that provides a tool for subscribing users to a Beehiiv newsletter using FastMCP. ## Installation You can install the package and its dependencies using pip (or uv/uvx): ```bash pip install . # or uv pip install . ``` Or, if published to PyPI: ```bash pip install mcp-server-beehiiv # or uv pip install mcp-server-beehiiv ``` ## Setup 1. Create a `.env` file in the project root with your Beehiiv credentials: ``` BEEHIIV_PUBLICATION_ID=your_publication_id BEEHIIV_API_KEY=your_api_key ``` ## Running the Server To start the MCP server, run: ```bash python -m mcp_server_beehiiv ``` ## Using the Tool The server exposes a tool called `subscribe_to_newsletter` with the following parameters: - `email` (required): The email address of the subscriber - `first_name` (optional): The subscriber's first name - `last_name` (optional): The subscriber's last name The tool will return the response from the Beehiiv API upon successful subscription. ## Security Note Never commit your `.env` file or expose your API keys. The `.gitignore` file is configured to prevent accidental commits of sensitive information.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.