Buttondown MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Marketing & social media

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://buttondown.usefulapi.io/mcp

claude mcp add --transport http buttondown https://buttondown.usefulapi.io/mcp

{
  "mcpServers": {
    "buttondown": {
      "url": "https://buttondown.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "buttondown": {
      "type": "http",
      "url": "https://buttondown.usefulapi.io/mcp"
    }
  }
}

https://buttondown.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• buttondown_get_account

  The Buttondown account this API key belongs to: username and e-mail address. GET /accounts/me.

• buttondown_list_newsletters

  List the newsletters on the account with name, username, domains, sender, locale and timezone. The newsletter's API key, custom CSS and e-mail templates are never returned. GET /newsletters.

• buttondown_get_newsletter

  One newsletter by id (settings and identity only; no API key, CSS or templates). GET /newsletters/{id}.

• buttondown_list_subscribers

  List or search subscribers (newest first by default) with e-mail, type (regular, unactivated, unsubscribed, premium, ...), tags, notes, metadata, source, open/click rates and dates. Filter by e-mail text, type, tag, signup date or domain. GET /subscribers.

• buttondown_get_subscriber

  One subscriber by id or by e-mail address: type, tags, notes, metadata, source, engagement and lifecycle dates. GET /subscribers/{id_or_email}.

• buttondown_add_subscriber

  WRITE: add ONE subscriber by e-mail address. No subscriber type is set, so Buttondown applies the newsletter's normal sign-up rules (double opt-in: the subscriber is typically created as unactivated and Buttondown e-mails THAT ONE address a confirmation message; opt-in is never b

• buttondown_update_subscriber

  WRITE: change ONE subscriber's tags, private note or metadata. Tags are merged (add_tags / remove_tags change only those names; the others stay). A given note or metadata replaces the existing value (destructive for that field). The subscriber's type (unsubscribe, block, ...) and

• buttondown_list_emails

  List emails (drafts, scheduled and sent), newest first by default, with subject, status, publish date, slug, archive URL and analytics summary. The body is left out unless include_body is set. Filter by status, subject text or date. GET /emails.

• buttondown_get_email

  One email by id with its full body, subject, status, publish date, slug, archive settings and analytics summary. GET /emails/{id}.

• buttondown_get_email_analytics

  Delivery and engagement numbers for one sent email: recipients, deliveries, opens, clicks, failures, unsubscriptions, complaints, replies, page views. GET /emails/{id}/analytics.

• buttondown_create_email_draft

  WRITE: create a DRAFT email (status always "draft"). Nothing is sent or scheduled and no subscriber is e-mailed; to send it, the user must open the draft in Buttondown and send it there. This server has no tool that sends or schedules email. Body is Markdown or HTML. POST /emails

• buttondown_update_email_draft

  WRITE: edit the subject, body, description, slug or preview image of an email that is still a DRAFT (replaces those fields; the previous text is lost unless Buttondown's email history is used). Refuses any email that is not a draft, and never changes status or publish date, so no

• buttondown_list_tags

  List subscriber tags with name, color, descriptions and whether subscribers can edit them. GET /tags.

• buttondown_get_tag_analytics

  Subscribers created, open rate and click rate for one tag. GET /tags/{id}/analytics.

• buttondown_create_tag

  WRITE: create a subscriber tag (needs a Buttondown plan with tags). An existing tag with the same name is returned as an error and not changed. POST /tags.

• buttondown_list_automations

  List automations (welcome sequences and other triggered e-mails) with name, status, trigger, actions and filters (webhook URLs in actions are shown by host only). Read-only: automations are not started or changed. GET /automations.

• buttondown_get_automation

  One automation by id with its trigger, actions and filters. GET /automations/{id}.

• buttondown_get_automation_analytics

  Performance numbers for one automation. GET /automations/{id}/analytics.

• buttondown_list_surveys

  List surveys with question, answers, status and response count. GET /surveys.

• buttondown_list_survey_responses

  List survey responses (who answered what), optionally for one survey, email or subscriber. GET /survey_responses.

• buttondown_list_segments

  List saved subscriber segments with name, description and filters. GET /segments.

• buttondown_list_forms

  List sign-up forms with title, slug, status, tags and subscriber counts. GET /forms.

• buttondown_list_snippets

  List reusable content snippets with identifier, name, mode and how often each is referenced. GET /snippets.

• buttondown_list_webhooks

  List configured webhooks with status and subscribed event types. The signing key is never returned and the URL is shown by host only. GET /webhooks.

• buttondown_list_events

  List delivery events (delivered, opened, clicked, bounced, unsubscribed, ...), newest first, optionally for one email or subscriber. GET /events.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 142 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 25 tool descriptions and found no hidden instructions to the AI

Compared with others in Marketing & social mediai

• More stars than 0% of the other 2956 servers in this category
• Published to the registry more recently than 97% of the other 2956 servers in this category
• Basic checks equal to or better than 100% of the other 2956 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{