MCP server for Buttondown email newsletter API
MCP server for Buttondown email newsletter API. That is what the buttondown mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
An MCP (Model Context Protocol) server for interacting with the Buttondown newsletter API.
The server publishes 3 tools. What each one is for:
Emails — The Emails tool exposed by this serverSubscribers — The Subscribers tool exposed by this serverTags — The Tags tool exposed by this serverConfiguration is passed through the environment: BUTTONDOWN_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as buttondown-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Buttondown's toolset — Emails, Subscribers, Tags — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Buttondown's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Emails | The Emails tool exposed by this server. |
| Subscribers | The Subscribers tool exposed by this server. |
| Tags | The Tags tool exposed by this server. |
{
"mcpServers": {
"buttondown": {
"command": "npx",
"args": ["-y", "buttondown-mcp"],
"env": {
"BUTTONDOWN_API_KEY": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| BUTTONDOWN_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.