Integrations
Beyond serving HTML, Accent CMS exposes its content and management capabilities to non-browser clients.
MCP (Model Context Protocol)
MCP connects AI assistants to your Accent CMS content. When an AI tool like Claude Desktop is configured as an MCP client, it can read pages, create new posts, update frontmatter, and run validation – all through natural language prompts.
Use MCP when your workflow involves AI-assisted content authoring. Think “Claude manages your blog posts.” MCP requires a Pro license key.
Programmatic Access (JSON REST API)
For machine-to-machine access from your own code, Accent CMS serves a read-only
JSON REST API that mirrors the public content query surface. It returns the same
page metadata, hierarchy, and listings the templates see, as JSON, turning any
site into a headless CMS for decoupled frontends. The REST API is read-only and
requires no license key – it is available whenever api.enabled: true is set.
See the API Reference for the available endpoints and response shapes.
When to Use Which
| MCP | JSON REST API | HTTP (default) | |
|---|---|---|---|
| Purpose | AI assistant integration | Programmatic content access | Human-readable website |
| Client | Claude Desktop, AI tools | Any HTTP client | Web browser |
| Auth | Pro license key | None (public, read-only) | None (public) |
| Data format | JSON (MCP protocol) | JSON | HTML |
| Use case | Content authoring via AI | Headless reads, custom frontends | Website serving |
The standard HTTP server continues to work with no license key.
In this section
-
MCP Server
Use AI assistants to query your Accent CMS content via Model Context Protocol.
-
CDN Integration
Serve assets from a CDN, proxy web fonts privately, and coordinate cache purges.