# Buttondown Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Buttondown

Manage your Buttondown newsletter subscribers, emails, tags, automations and analytics.

- Record: https://musedirectory.ai/connector/buttondown
- Category: Marketing & Ads
- Developer: usefulapi (https://usefulapi.io/buttondown/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 341ms, checked 2026-10-29T10:45:49Z
- Endpoint: https://buttondown.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T08:01:41Z)
- Source: Found in the official MCP Registry (io.usefulapi/buttondown) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fbuttondown

Connect to Buttondown to read and manage subscribers, create and edit email drafts, view analytics, manage tags and automations, and track survey responses. Muse can help you add subscribers, update subscriber information, and draft newsletters.

Example request: "Add a new subscriber to my newsletter and tag them as a premium member."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Buttondown to help me. It is a free service with an MCP server at https://buttondown.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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.

Screening checks:
- MCP handshake: pass (Answered in 216ms)
- Domain against threat feeds (Cloudflare security DNS): pass (buttondown.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (25 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)