AI-native CMS with 41 MCP tools for managing websites through natural language.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"lightcms-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
LightCMS is a Go-powered content management system built for the AI era. It's simultaneously AI-native (semantic search, built-in Claude-powered chat widget, MCP server for agent control), agentically controllable (Claude Code and any MCP client can read, write, publish, and bulk-import content via 106 MCP tools), and agentically updatable (the codebase is clean, well-structured Go — coding agents can safely extend it). For teams that want a CMS that works with AI rather than around it.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
site_structureSite structure and organization
lightcms://site/structure
recent_contentRecently created or modified content
lightcms://content/recent
theme_configTheme configuration
lightcms://theme/config
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / writing
Dynamic problem-solving through sequential thought chains
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Persistent memory using a knowledge graph
MCP server for monday.com integration.
MCP Security Weekly
Get CVE alerts and security updates for Lightcms MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
LightCMS is a Go-powered content management system built for the AI era. It's simultaneously AI-native (semantic search, built-in Claude-powered chat widget, MCP server for agent control), agentically controllable (Claude Code and any MCP client can read, write, publish, and bulk-import content via 106 MCP tools), and agentically updatable (the codebase is clean, well-structured Go — coding agents can safely extend it). For teams that want a CMS that works with AI rather than around it.
| Feature | Summary |
|---|---|
| Ambient Copilot | The copilot is a slide-in drawer on every admin page — floating 🤖 button, fullscreen toggle, ChatGPT-style searchable chat history, live typing indicator, and rendered tables. It edits, creates, publishes, and reads analytics and maintenance reports in plain language. |
| Analytics Ranges | 60/90-day presets and custom date ranges across all analytics views. |
| Fast AI-Crawler Endpoints | llms.txt serves in ~1 second on large sites (projected queries), and homepages emit schema.org WebSite JSON-LD with SearchAction. |
| Version Visibility | The admin sidebar shows the running version. |
| Feature | Summary |
|---|---|
| Agent Sandbox ("PRs for content") | Agents work in an isolated fork with copy-on-write; humans review a per-field diff and merge. Live content is untouchable until merge. |
| Agent Governance | Scoped API keys, sandbox-only keys (server-enforced), per-session change ledger with one-call rollback, and per-version provenance (human vs agent, which session). |
| Admin Copilot | /cm/copilot — edit, create, and publish content in plain language, with RBAC and full audit logging. |
| llms.txt + JSON-LD | Auto-generated /llms.txt and /llms-full.txt for AI crawlers, schema.org structured data on every page. |
| MCP for Readers | Public read-only MCP endpoint at /mcp-public — visitors' agents can search and read the site natively. |
| Local Embeddings | LIGHTCMS_EMBEDDINGS_PROVIDER=ollama for fully self-hosted semantic search — no API credits. |
| Self-Maintaining Sites | Daily maintenance scans surface stale pages, missing meta, and broken links as an agent-ready work queue. |
| Feature | Summary |
|---|---|
| Content Approvals | Contributors submit content for approval; editors/admins approve or reject from /cm/approvals. Rejection comments auto-post to the discussion thread. |
| Contributor Role | New RBAC role between Viewer and Editor. Can create content + upload assets (pending), post comments, and submit for approval — but cannot publish directly or manage system settings. |
| Approval Workflows | Configurable trigger-based workflows (contributor, folder path, template ID, or tag). Sequential or concurrent mode with configurable approver lists. |
| Content Discussion | Inline comment thread at the bottom of every edit page. @mention autocomplete, live badge count, admin delete. |
| Tabbed Bottom Panel | Discussion, Version History, and Forks organized into tabs on the content edit page. |
| Approvals Dashboard | My Queue + Other Pending + Workflow Config at /cm/approvals. Sidebar badge shows pending count. |
| Dashboard Sections | Requiring Approvals and Recent Comments appear on the admin dashboard when relevant. |