Buttondown MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUTTONDOWN_API_KEY | Yes | Your Buttondown API key. Get it from https://buttondown.com/settings/api |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_emailsA | List emails from your Buttondown newsletter. Filter by status (draft, scheduled, sent, etc.) |
| get_emailC | Get detailed information about a specific email |
| create_draftB | Create a new draft email with markdown content |
| update_draftB | Update an existing draft email |
| send_draftA | Send a draft email immediately to subscribers |
| schedule_draftA | Schedule a draft email to be sent at a specific time |
| get_analyticsA | Get analytics for a sent email (open rates, click rates, etc.) |
| list_subscribersB | List subscribers from your Buttondown newsletter. Filter by subscriber type. |
| get_subscriber_statsA | Get aggregate subscriber statistics with counts broken down by type (regular, premium, churned, etc.). Much more efficient than listing all subscribers. |
| list_tagsB | List all tags in your Buttondown newsletter |
| get_subscriberA | Get detailed information about a specific subscriber by ID or email address |
| get_tagA | Get detailed information about a specific tag |
| create_tagA | Create a new tag to organize subscribers |
| update_tagA | Update an existing tag |
| delete_tagA | Delete a tag (subscribers with this tag will not be deleted) |
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 15 tools
Each tool targets a distinct resource and action, such as list_emails vs. get_email, and send_draft vs. schedule_draft. The only potential overlap is list_subscribers and get_subscriber_stats, but the descriptions clearly differentiate aggregate stats from listing individuals.
Tool names follow a consistent verb_noun pattern: list_* for listing, get_* for single-item retrieval, and create_/update_/delete_/send_/schedule_ for actions. Singular nouns are used for single-item operations, plural for lists, with minor exceptions like get_analytics and get_subscriber_stats that still fit the pattern.
With 15 tools, the server is at the upper end of a well-scoped range but covers a broad domain: emails, drafts, subscribers, tags, and analytics. Each tool serves a clear purpose, though the count could be trimmed by merging some read operations.
The main workflows are covered: create, update, send, and schedule drafts; list and get emails; and full CRUD for tags. However, there is no delete_draft action, and subscriber management is limited to reading and stats, leaving gaps in lifecycle management.