Articles

Add MCP server to your AI tool

Allow AI tools and LLMs to interact with the API documentation portal through MCP.

MCP server URL

https://api-reference.usecommune.dev/mcp

Standard setup for AI tools providing an mcp.json file

mcp.json
{
  "REST API MCP server": {
    "url": "https://api-reference.usecommune.dev/mcp"
  }
}

Close

An article is one thing a newsletter published: written in Commune and sent, or imported from the newsletter's provider. Two rules gate every article read and are described on each operation. First, an article stamped with an audience is visible only to the newsletter's team and to subscribers holding one of its tags. Second, an article dated in the future is invisible until that moment passes.

An article written in Commune can be created and edited here, its body sent and returned as Markdown, and moved through its life: sent to a test address, queued for a time, taken back off the schedule, sent to the list, and re-attempted for the recipients a dispatch could not reach. An imported article is read only.

What one reader did with an article is here too, from their side of it. GET /saved-articles and GET /liked-articles are the articles an account put aside and the articles it liked, across every newsletter it reads, and they need account: read rather than content. Both obey the two rules above, applied against the person rather than against a newsletter, so an article they may no longer read leaves the page on its own.