Fetching this document

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

This contract is served by the API itself, in two syntaxes carrying the same content: https://api.usecommune.com/openapi.yaml and https://api.usecommune.com/openapi.json. Generate a client from whichever your toolchain prefers.

?version= selects a contract version, the same way the Commune-Version header does for a request, and answers 404 for a version that was never released. ?profile=docs returns the variant the published reference is rendered from; it differs only in presentation metadata, so the operations, webhooks and schemas are identical either way. The one difference in the prose is where it sits: that variant moves each section of info.description, this one included, into x-topics, so the reference can list them in its navigation, and leaves info.description holding only the opening paragraphs.

Example
curl https://api.usecommune.com/openapi.yaml

curl "https://api.usecommune.com/openapi.json?version=2026-08-26"

curl "https://api.usecommune.com/openapi.yaml?profile=docs"