RenewCMS/docs/releases/v3.5.2-beta.md

This release lets language models read and use a RenewCMS instance: the server publishes its own documentation, an OpenAPI description, and a separate MCP server drives the API with a key.

New

Documentation for language models

• Every instance serves /llms.txt (a short index), /llms-full.txt (all the documentation in one file), /llms/<page>.md (one page each) and /openapi.json. They are public, and carry the version and address of the instance that serves them.
• The pages include the API reference, the API key and article guides, ready-to-run recipes with real responses (publish an article, upload and attach an image, sites and sitemaps, pagination and formats), and a gotchas page on session-only routes, error texts, rate limits and draft visibility.

MCP server

• The new renewcms-mcp binary is a stdio MCP server for Claude Desktop, Claude Code, Cursor and similar clients. It calls the public API with an API key, so the key's rights limit what the model can do.
• Tools: list, get, create, update the body of and publish articles, check SEO, list and upload media, list sites and read a sitemap. Deletion tools are only offered with --allow-destructive.
• It exposes the instance's llms-full.txt as a resource and a prompt that drafts, checks and asks before publishing. Setup is in docs/mcp.md.

API

• GET /llms.txt, GET /llms-full.txt, GET /llms/{page} and GET /openapi.json are public routes outside /v1. They answer 404 with a notice when the build did not generate them.

Under the hood

• The API reference and openapi.json are generated from web/src/data/apiCatalogue.ts by task build:llms, which task build, task release and the Docker image run first.
• A new test fails when a route of the router is missing from the catalogue. Twenty-five existing routes (content types, entries, builtin types, image variants, media variants and the user lookup) are still undocumented and listed as exceptions in that test.
• The catalogue now records the success status of each endpoint.
• task build:mcp builds the MCP server. task release does not include it yet.

Upgrading

• Replace the binary, or pull the new image. No schema migration and no new environment variable.
• The MCP server reads RENEWCMS_URL and RENEWCMS_API_KEY in its own process; the server does not need them.