Buttondown MCP server

What the model can do

Buttondown newsletter: subscribers by type, tag or signup date with engagement, emails (drafts, scheduled and sent) with opens and clicks, comments, events, tags and private notes. Can write and edit draft emails, send a draft to named people, publish a draft to its audience, send one email to one subscriber, add, update or delete subscribers, update or delete tags and emails, moderate comments, add a private note and create a tag.

Reads

• buttondown_list_subscribersNewsletter subscribers: email, type (regular, premium, unsubscribed, churned…), tags, signup date, open and click rates, last open and click…
• buttondown_get_subscriberOne subscriber by id or email address, with the same fields as the list and their private notes.
• buttondown_list_emailsNewsletter emails (drafts, scheduled, sent): subject, status, created, modified and published dates, archive URL, and recipients, deliveries, opens…
• buttondown_email_analyticsAnalytics for one sent email: recipients, deliveries, opens, clicks, unsubscriptions and the rest Buttondown reports.
• buttondown_list_tagsThe newsletter's tags: name, colour, internal description and whether subscribers can set it themselves.
• buttondown_list_commentsComments readers left on emails: who, on which email, when, status and the text cut to 600 characters.
• buttondown_list_eventsDelivery and engagement events (delivered, opened, clicked, unsubscribed…) for one email or one subscriber, newest first.
• buttondown_list_notesPrivate notes the writer keeps on a subscriber, email or other record.

Acts, when you ask

These change something in Buttondown. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• buttondown_create_noteAdds a private note to a Buttondown subscriber, email, tag, comment, automation, survey or conversation.
• buttondown_create_tagCreates a Buttondown tag with a name, a colour and an optional internal description.
• buttondown_create_draft_emailWrites a new Buttondown email as a draft.
• buttondown_update_emailEdits a Buttondown email's subject, body, description, slug, canonical URL, comment setting or featured flag.
• buttondown_send_draftSends a draft email to the named subscribers or email addresses only (at most 20 of each), for example a test send to the team.
• buttondown_publish_emailPublishes a draft Buttondown email now, which emails every subscriber matching the email's audience filters and puts it in the archive per its…
• buttondown_send_email_to_subscriberSends one existing Buttondown email to one subscriber, who receives it in their inbox.
• buttondown_create_subscriberAdds a subscriber to the newsletter.
• buttondown_update_subscriberChanges a subscriber's email address, private notes, tags, type (regular or unsubscribed, which stops their emails) or whether they may comment.
• buttondown_delete_subscriberPermanently deletes a subscriber and their record from the newsletter.
• buttondown_delete_emailPermanently deletes a Buttondown email; a sent one disappears from the archive.
• buttondown_update_tagRenames a Buttondown tag or changes its colour or internal description.
• buttondown_delete_tagPermanently deletes a Buttondown tag; it is removed from every subscriber who carries it and from any email audience that uses it.
• buttondown_moderate_commentApproves a reader's comment (status active, which makes it visible to readers) or marks it as spam (spammy, which hides it).

Connect it

First connect Buttondown on Dashboard → Connections, then add Memtro to your client once. The Buttondown tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Buttondown connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How many people subscribed this month?
• › How did last week's issue do on opens and clicks?
• › Why did subscribers unsubscribe in March?
• › What did readers say in the comments on the latest email?
• › Send the draft of Friday's issue to Priya and me as a test

Questions

Is this an official Buttondown MCP server?

No. It is Memtro's MCP server with Memtro's Buttondown connector behind it: the connector reads Buttondown through its API with the credentials you connect on Dashboard → Connections, and Buttondown publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Buttondown?

Only when you ask, and only what it has been granted: add a private note to a subscriber, email or other record; create a tag (refused if the name already exists); write a new email as a draft (never sent by this); edit an email's subject, body, description, slug or comment setting (never its status or schedule); send a draft to named subscribers or addresses (they receive it); publish a draft, emailing every subscriber in its audience; send one existing email to one subscriber; add a subscriber (refused if the address exists); update a subscriber's email, notes, tags or type, including unsubscribing them; delete a subscriber (permanent); delete an email (permanent); rename or recolour a tag; delete a tag (permanent); approve a reader comment or mark it as spam. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Marketing automation

• ActiveCampaign MCP server
• Brevo MCP server
• Customer.io MCP server
• Marketo Engage MCP server
• Account Engagement (Pardot) MCP server
• Mailchimp MCP server