Beehiiv Analytics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEEHIIV_API_KEY | Yes | Your Beehiiv API key from the developer portal |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_publicationsC | Get list of publications |
| get_publication_detailsC | Get detailed information about a specific publication |
| get_postsC | Get posts for a publication |
| get_post_detailsB | Get detailed information about a specific post |
| get_subscribersC | Get subscribers for a publication |
| get_subscriber_detailsC | Get detailed information about a specific subscriber |
| get_segmentsC | Get segments for a publication |
| get_segment_detailsC | Get detailed information about a specific segment |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose targeting different resources (posts, publications, segments, subscribers) with consistent get_<resource> and get_<resource>_details patterns. There is no ambiguity between tools as each serves a unique data retrieval function.
All tools follow a perfectly consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming convention is predictable throughout the set, making it easy to understand each tool's function at a glance.
With 8 tools, this server is well-scoped for analytics purposes. Each tool earns its place by covering different data retrieval aspects of the Beehiiv platform, providing comprehensive read access without being overwhelming.
The toolset provides excellent read coverage with consistent get operations for all major resources, but lacks any write, update, or delete capabilities. For an analytics server, this may be intentional, but it creates a read-only surface that limits agent workflows to data retrieval only.