Skip to content

Commune

Official status unknown30 tools reported1 source

Commune turns newsletters into communities. This server connects Claude to the newsletters you run on Commune, so you can ask about them in plain language and act on them without opening a dashboard. - Performance: how your latest article or any specific one did, how the newsletter is doing overall, where new subscribers came from, and how a single metric has changed over time. - Readers: your most engaged readers, readers who are drifting away or warming up, recent reader activity, and who is on your list. - Community: what people are discussing right now, the full text of any conversation, what readers said under an article, and the passages they highlighted. - Publishing: draft and revise articles, send yourself a test copy, schedule or send to your list, and confirm the last send went out. - Setup: your team, the newsletters you can reach, and why a custom domain isn't live yet. Two general-purpose tools, commune_read and commune_write, cover every other endpoint of the Commune API. Reads are marked read-only so Claude can run them without asking you each time. Anything that changes data is marked destructive and needs an idempotency key, so a retry never runs the same change twice. Sending emails real subscribers and can't be undone, so Claude confirms with you first. Each credential grants none, read or write per newsletter in six areas: content, audience, sending, insights, settings and webhooks. The server can only reach what that credential allows.

Connection details

  • Remote endpoint

    Official status unknown

    Transport not established · Authentication not established

    https://api.usecommune.com/mcp

    Use the source documentation for installation instructions. No command has been inferred.

    Connection source and version

    Reported by Claude logoClaude connector directory

30 tool names reported

Source-declared tools. Availability can depend on the connection and permissions; these are not runtime test results.

Claude connector directory ↗ · Observed 2026-11-01 · Completeness not established

  • chart_one_number_over_time
  • commune_read
  • commune_write
  • did_my_last_send_go_out
  • draft_an_article
  • find_something_across_commune
  • find_superfans
  • how_did_my_latest_article_do
  • how_did_this_article_do
  • how_is_my_newsletter_doing
  • is_my_website_domain_live
  • look_up_a_newsletter
  • read_a_conversation_end_to_end
  • read_one_article_in_full
  • revise_an_article
  • schedule_an_article
  • send_a_test_copy
  • send_an_article_now
  • what_are_readers_actually_doing
  • what_are_readers_saying_about_this_article
  • what_did_i_publish_recently
  • what_did_readers_highlight_in_this_article
  • what_have_i_not_sent_yet
  • what_is_my_community_talking_about
  • where_are_new_subscribers_coming_from
  • which_newsletters_can_i_reach
  • who_can_act_on_my_newsletter
  • who_is_drifting_away
  • who_is_on_my_list
  • who_is_warming_up

Sources and provenance

Grouping basis: endpoint. Exact endpoints or package sets can be grouped automatically; other relationships require evidence review. This does not verify publisher affiliation, connection health, or equivalent capabilities.

Search API Tracker

Curated starting points