Keys that follow the role.
Named API keys inherit their creator’s current permissions. Revoke keys from the workspace. Keep privileged keys on your server.
Read the docs (opens in a new tab)The content is ready.
The frontend is yours.
Give editors a home they enjoy. Keep the stack you love. Read articles through a REST API and bring them into your website, app or publishing workflow.
Read the API reference (opens in a new tab)Pick your format.
Keep your flow.
Markdown by default. Stored HTML when you want it. Structured JSON blocks when you need control over rendering. Switch formats to inspect an example response.
RenewCMSYour frontend
One article. Your format.ILLUSTRATIVE RESPONSE
GET
/v1/article/1?format=markdown200 OK{
"id": 1,
"title": "Notes from the field",
"body": "## A different pace\n\nMake space for **good ideas**.",
"body_format": "markdown",
"is_online": true,
"site_id": 1,
"slug": "notes-from-the-field"
}Same content. No frontend imposed.Full reference (opens in a new tab)
SEO, already resolved.
Fetch canonical URLs, Open Graph, Twitter cards and Article JSON-LD, with site defaults applied. Your frontend renders the tags.
Read the docs (opens in a new tab)A contract you can inspect.
Each instance serves version-matched OpenAPI 3.1 documentation, /llms.txt and /llms-full.txt, plus a searchable API reference in the workspace.
Read the docs (opens in a new tab)Published articles can be read without a key. Draft visibility follows the caller’s permissions. Custom entries require authentication. Some administration routes require a browser session.
A connection for
your other assistant.
The separate renewcms-mcp server connects compatible MCP clients to your instance. List articles, prepare drafts, upload media and check SEO through the same HTTP API.
The API key’s permissions remain the limit. Destructive tools are disabled by default. The supplied writing prompt asks before publishing.
Explore the MCP setup (opens in a new tab)Your MCP clientstdio
↓renewcms-mcpSeparate binary
↓ Authorization: Bearer rcms_…
Your RenewCMS instanceHTTP APIOne home for content.
Many ways forward.
Use articles for editorial work and custom types for structured entries. Build projects, directories or collections with media and relations, using the generic content API.
RenewCMS manages your content. You build and host the public frontend, including its rendering, routes and deployment.
Put the backend on your serverMake room for
your next good idea.
Currently in beta. Self-hosted, with source code you can explore.