Buttondown MCP Server
Related Servers
Alternatives to Buttondown MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables interaction with the Buttondown newsletter API for managing emails, subscribers, and tags.1532 npm1MIT

Tratto MCP Serverofficial
FlicenseAqualityFmaintenanceLets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.2-
@sendbyte/mcpofficial
AlicenseAqualityDmaintenanceEnables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.1113 npmMIT- AlicenseBqualityCmaintenanceEnables natural language management of Motion tasks, projects, schedules, and more by bridging the Motion API with LLMs through the Model Context Protocol.10Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.-
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables Large Language Models (like Claude) to interact with Beehiiv publications and posts through standardized tools and the Beehiiv API v2.54-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose targeting specific actions in the email lifecycle: create_draft for creation, list_emails for listing, get_analytics for analytics retrieval, and schedule_draft for scheduling. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case (create_draft, get_analytics, list_emails, schedule_draft). The verbs are appropriate and predictable, making the set easy to understand and use.
With 4 tools, the count is reasonable for an email newsletter server, covering core operations. However, it feels slightly thin as it lacks tools for updating or deleting drafts, which are common in such domains, but the scope is still well-defined.
The tool set covers key email lifecycle stages: creation, listing, analytics, and scheduling. Minor gaps exist, such as no update_draft or delete_draft tools, but agents can work around this by creating new drafts or using existing ones, and the core workflow is supported.