Buttondown MCP Server
Used for securely storing and retrieving API keys, specifically integrating with the Buttondown API by fetching credentials from a specific 1Password path.
Supports creating email content in Markdown format when creating newsletter drafts through the Buttondown API.
Supported as an alternative package manager for installing and managing the Buttondown API integration package.
Recommended package manager for installing and managing the Buttondown API integration package and its dependencies.
Provides full TypeScript support with comprehensive type definitions and real API response-based types for the Buttondown newsletter service integration.
Supported as an alternative package manager for installing and managing the Buttondown API integration package.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Buttondown MCP Server create a draft newsletter about our Q3 product updates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Buttondown API Integration
A comprehensive TypeScript integration for the Buttondown newsletter service, providing both a CLI interface and a Model Context Protocol (MCP) server for managing newsletters, drafts, and analytics.
Features
Multiple Interfaces:
Command Line Interface (CLI) for direct interaction
Model Context Protocol (MCP) server for AI/LLM integration
Programmatic TypeScript API for custom integrations
Core Functionality:
Email draft management (create, update, delete)
Email scheduling system
Analytics retrieval and formatting
List management
Tag management
Security:
1Password integration for API key management
Environment variable support
Secure credential handling
Developer Experience:
Full TypeScript support
Comprehensive type definitions
Real API response-based types
Built-in testing utilities
Related MCP server: Buttondown MCP Server
Installation
# Install using pnpm (recommended)
pnpm install
# Or using npm
npm install
# Or using yarn
yarn installConfiguration
The API key can be provided in two ways:
Environment variable:
export BUTTONDOWN_API_KEY=your_api_key1Password CLI (recommended):
Store your API key in 1Password at
op://Development/Buttondown API/notesPlainThe integration will automatically fetch it when needed
Usage
CLI Interface
# List all emails
buttondown emails list
# Create a new draft
buttondown draft create <file>
# Schedule an email
buttondown schedule set <draft-id> <relative-time>
# Get analytics
buttondown analytics get <draft-id>MCP Server
Start the server:
pnpm mcp:startStart with inspector (for development):
pnpm mcp:inspect
Available MCP tools:
list_emails: List all emails with optional status filtering{ "status": "draft" // Optional: "draft", "scheduled", "sent" }create_draft: Create a new email draft{ "content": "Email content in markdown", "title": "Optional email subject" }get_analytics: Get analytics for a specific email{ "draftId": "email-id-here" }schedule_draft: Schedule an email for sending{ "draftId": "email-id-here", "scheduledTime": "2024-03-27T10:00:00Z" }
Programmatic Usage
import { ButtondownAPI } from "api-integrator";
// Initialize the client
const api = new ButtondownAPI(); // Will use 1Password or env var
// List drafts
const drafts = await api.getDrafts();
// Create a draft
const draft = await api.createEmail({
subject: "My Newsletter",
body: "Content here",
status: "draft",
});
// Schedule an email
const scheduled = await api.scheduleEmail(draft.id, "2024-03-27T10:00:00Z");
// Get analytics
const analytics = await api.getEmailStats(draft.id);Development
# Build the project
pnpm build
# Run tests
pnpm test
# Start MCP server in development mode
pnpm mcp:inspect
# Build MCP server
pnpm mcp:buildTesting
The project includes several types of tests:
Unit tests for core functionality
Integration tests for API interactions
CLI command tests
MCP server tests
Run tests with:
pnpm testProject Structure
.
├── src/
│ ├── api/ # Core API client
│ ├── cli/ # CLI implementation
│ ├── mcp/ # MCP server
│ ├── types/ # TypeScript definitions
│ └── utils/ # Shared utilities
├── tests/ # Test files
├── api-responses/ # Cached API responses
└── memory-bank/ # Project documentationContributing
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
License
ISC License - See LICENSE for details
Acknowledgments
Buttondown for their excellent newsletter service
Model Context Protocol for the AI integration framework
Available Tools
4 toolscreate_draftA
Create a new email draft in Buttondown with the specified content and optional title. This tool requires explicit user confirmation before proceeding as it will create a new draft in your Buttondown account.
Inputs: content (required), confirmed (required), title.
get_analyticsC
Retrieve analytics data for a specific email draft from Buttondown
Inputs: draftId (required).
list_emailsB
List all emails, optionally filtered by status (draft, scheduled, sent)
Inputs: status.
schedule_draftA
Schedule an existing email draft to be sent at a specific time. This tool requires explicit user confirmation before proceeding as it will modify the draft's status and schedule.
Inputs: draftId (required), scheduledTime (required), confirmed (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Read Buttondown subscribers, emails, analytics and automations; add subscribers; write email drafts.
Manage beehiiv newsletters, posts, podcasts, community, subscribers, and analytics.
Connect AI agents to Emitd email sending, message tracking, templates, and automations. Emitd hosts a Model Context Protocol server for integrating supported email operations into AI-agent workflows. Connect a compatible client to the hosted endpoint (https://mcp.emitd.com/mcp) and authenticate with an Emitd API key. Available tools depend on the key's permissions and enabled features. Emitd's capability areas include sending email, message activity, templates, contacts, audiences, segments, domains, analytics, inbound email, broadcasts, automations, webhooks, and suppressions. Use restricted keys, sending guardrails, and approval settings appropriate to each workflow. For more information check https://emitd.com
Draft, schedule, and analyze content for Substack, Medium, LinkedIn, X, Bluesky, and Threads.
Related MCP Servers
- 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-
- AlicenseAqualityDmaintenanceEnables interaction with the Buttondown newsletter API for managing emails, subscribers, and tags.1534 npm1MIT

@sendbyte/mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.1112 npmMIT- AlicenseBqualityNot gradedmaintenanceEnables 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