LightCMS is a Go-powered content management system built for the AI era. It's simultaneously (semantic search, built-in Claude-powered chat widget, MCP server for agent control), (Claude Code and any MCP client can read, write, publish, and bulk-import content via 130 MCP tools), and (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.
AI-native, open-source CMS (Go) with 128 MCP tools: content, agent sandbox, SEO & AI.
stdio
버전
7.3.4
API 키
LIGHTCMS_URL, LIGHTCMS_API_KEY
마지막 확인
2026-11-09
스타
—
도구
—
가동 시간
—
AI-native
agentically controllable
agentically updatable
What's New in v7.3 — SEO & AI
Feature
Summary
AI Traffic
See which AI crawlers read your site (training vs. AI search vs. user-initiated fetches), what they read most, and how many visits ChatGPT, Perplexity, Claude, Gemini and Copilot send you.
AI Crawler Policy
Allow or block AI training, AI search and user fetches separately, with per-crawler overrides and an optional Content-Signal line, rendered into robots.txt.
Markdown Copies
Every page is also available as clean Markdown at /<page>.md, linked from the page and from llms.txt, so agents can read it without the HTML.
Richer Structured Data
Authors, publisher with logo, breadcrumbs, FAQ markup, and modified dates that only move when the page content actually changes.
RSS & Atom Feeds
/feed.xml, /atom.xml and per-collection feeds with full content.
Hide from Search & AI
Per-page noindex that also removes the page from the sitemap, llms.txt, feeds and IndexNow.
What's New in v7.2
Feature
Summary
IndexNow
Published, edited, moved and deleted pages are pushed to Bing, Yandex and other IndexNow engines right away. Zero-config: each install generates its own key, verifies it owns its BASE_URL before submitting, and submits the whole site once on first activation. Status and history at Tools → IndexNow.
CMS Agent
Configurable email digests (via Resend) covering site health, traffic, review queue, agent activity and broken links, with optional AI commentary.
What's New in v7.1
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.
What's New in v7.0
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.
What's New in v6.0
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.
import_markdown is designed for AI agents to generate and import large content batches in a single call. See MCP.md.
Deduplication
Imports match by full_path — re-importing the same slug updates rather than duplicates.
What's New in v4.5
Feature
Summary
Webhooks
HMAC-SHA256 signed events for publish, unpublish, delete, create, update. Admin UI at /cm/webhooks with delivery history and a docs page.
Scheduled Publishing
Set a future publish_at timestamp on any content item; a background scheduler auto-publishes at the right time.
Content Locking
Advisory lock when editing (30-min expiry). Warning banner if another user is already editing. Admins can force-unlock.
Incremental Static Regeneration (ISR)
Template layout changes regenerate affected pages in 20-page batches, preventing server overload on large sites.
Edge Caching Headers
ETag, Cache-Control, Last-Modified, and Vary headers on all public pages. 304 Not Modified support.
Cloudflare Integration
Configure Zone ID + API Token to auto-purge Cloudflare cache on publish/unpublish.
Structured JSON Logging
All server logs emit structured JSON with timestamp, level, message, and context fields.
Rate Limit Dashboard
New tab on the audit log page showing locked IPs, attempt counts, and a one-click clear button.
MCP Prompt Resources
Three new MCP resources: lightcms://site/structure, lightcms://content/recent, lightcms://theme/config.
Why LightCMS?
Lightweight: A clean, focused codebase that's easy to understand, modify, and extend. No bloated frameworks or complex abstractions.
AI-Native: Built from the ground up for the AI era:
MCP Integration: Full Model Context Protocol server with 130 tools and 3 prompt resources for website management. Supports both local stdio and HTTP streamable transports — connect from Claude Code, Claude Desktop, or any MCP-compatible client.
OAuth 2.1 for Remote Agents: Sandboxed desktop apps like Claude's Cowork can securely connect over HTTP using OAuth 2.1 with PKCE. No embedded passwords — just authorize once and the agent manages your site.
Fork-Friendly: Designed to be forked and customized by Claude Code. Ask Claude to add new content types, modify templates, or build custom features — the codebase is structured for AI-assisted development.
Natural Language Website Management: Skip the admin UI entirely. Create pages, manage assets, customize themes, and publish content through conversation.
Rich Text Editor: Quill 2 for visual content editing (vendored in static/admin/quill/, served from the site itself)
Regex Search & Replace: Site-wide or scoped search-and-replace with RE2 regex support, capture groups, and mandatory preview step
Bulk Operations: Update or apply field operations across up to 100 pages in a single API call; export/transform/re-import pipelines
Scheduled Publishing (v4.5+): Set a future publish_at timestamp; a background scheduler auto-publishes at the right time
Content Locking (v4.5+): Advisory lock while editing (30-min expiry); warning banner if another user holds the lock; admins can force-unlock
Incremental Static Regeneration (v4.5+): Template layout changes regenerate pages in 20-page batches to prevent server overload on large sites
Import Pipeline (v5.0+)
RSS/Atom Feed Sources: Configure recurring import sources with configurable schedule (hourly/daily/weekly), template mapping, folder targeting, and auto-publish. Manage sources and run history from /cm/imports. Feed URLs must be publicly reachable (private and loopback addresses are refused, v7.4.3).
Markdown + ZIP Import: Upload .md files or .zip archives of Markdown. YAML frontmatter in each file controls title, slug, folder, template, tags, and scheduled publish time. Supports Notion exports, Obsidian vaults, Hugo/Jekyll site migrations, and AI-generated content.
CSV Bulk Import: Upload a CSV and specify which column is the title; all other columns are stored as content fields automatically.
Real-time SSE Job Status: Live log stream at /cm/imports/{jobID} — watch imports happen line-by-line or review full history after the fact.
MCP-first Design: import_markdown is specifically designed for AI agents to generate and import large content batches in a single call, replacing dozens of create_content calls with one import_markdown + one get_import_job. See MCP.md for workflow examples.
Content Forks (v4.0+)
Fork Workspaces: Create named staging workspaces where sets of page edits can be authored, previewed, and reviewed before going live
Sparse Model: Only edited pages live in a fork — unmodified pages fall through to live content automatically
Fork Preview Mode: Activate via a floating bar injected into the live site; a cookie routes all page requests through the fork so you see exactly how the site will look after merge
Merge with Conflict Detection: Admins merge forks into live content; if a live page was changed after the fork was created, the conflict is recorded (fork wins). New pages created in the fork are inserted into live on merge, keeping the publish state they had in the fork (normally draft) unless the merge is run with publish_new
Merges Clean Up (v7.4+): A merge deletes the fork's page copies and keeps the fork record, with created/updated counts, as history. Forks merged before v7.4 can be cleaned with purge_fork_copies
Fork Copies Stay Out of the Way (v7.4+): Fork copies are left out of content listings and search unless include_forks is set, and can never be published directly or in bulk — only merged
Hold Flag (v7.4+): Mark any draft hold to block every way of publishing it (publish, bulk publish, scheduled publish, approval, fork merge) until the flag is cleared
Designed for agents that prefer parallelized, high-throughput workflows over sequential single-item calls:
bulk_update_content: Update up to 100 pages in a single API call. Each item uses merge semantics — only the fields you specify are touched. Supports dry_run validation before committing, and auto_republish to re-publish all previously-published pages in the same call, eliminating a separate publish step
bulk_field_operation: Apply a single operation (set, clear, prepend, append, wrap) to a field across every matching page in one call. Scope by template, folder, category, or explicit ID list. Ideal for adding disclaimers, updating metadata, or clearing stale fields across a content type
publish_multiple: Publish a list of IDs — or all drafts at once with publish_all_drafts: true — in a single request instead of looping over publish_content
export_content: Dump full field data for a scoped set of pages as a structured JSON array. Designed for export → transform → re-import pipelines; pair with bulk_update_content for large-scale content migrations
Scoped Search & Replace: Both scoped_search_replace_preview and scoped_search_replace_execute accept scope filters (folder, template, category, IDs) so agents can target precise subsets rather than running site-wide operations
Parallel-Safe Read API: list_content with include_data: true returns full field values in one fetch; agents can fan out reads across multiple list_content / get_content calls concurrently and then batch-write with bulk_update_content
Recommended agent pattern for large updates: list_content → transform in parallel → bulk_update_content (up to 50/call) → publish_multiple.
AI Chat Widget (v4.2+)
Embeddable Widget: Add a floating AI chat bubble to any page with a single <script> tag — self-contained, no build step required
Two-Phase Pipeline: Each visitor query runs hybrid semantic+fulltext search to retrieve relevant content excerpts, then streams those excerpts through Claude Haiku for a conversational synthesized answer
SSE Streaming: Haiku's token-by-token output is forwarded live to the browser via Server-Sent Events; falls back to plain JSON for non-SSE clients
AI-Optional: Without an Anthropic API key, the widget works as a search-in-chat experience returning ranked excerpts — no API cost
Fully Configurable: Admin "Chat Widget" page controls title, welcome message, placeholder text, primary color, position (bottom-left/right), max results, and editable system/user prompt templates
Dedicated Rate Limiting: Separate per-IP (5/min) and global (30/min) limiters independent from the search and API limiters
Source Attribution: Every response includes the content pages whose excerpts were used, with titles and paths
Multi-User Access Control & Approvals (v2.0+, v6.0+)
Role-Based Access Control (RBAC): Four roles — admin, editor, contributor, viewer — with granular permission enforcement on all admin UI pages and REST API endpoints
Contributor Role (v6.0+): Create content, upload assets, post comments, and submit for editorial approval — without publish rights
Approval Workflows (v6.0+): Configurable trigger-based workflows (by role, folder, template, or tag). Sequential or concurrent mode. Default (no workflow): any editor or admin can approve
Content Approvals Dashboard (v6.0+): My Queue, Other Pending, and Workflow Config at /cm/approvals. Sidebar badge shows pending count
Content Discussion (v6.0+): Inline threaded comments on every content edit page. @mention autocomplete, admin delete, live count badge
User Management: Admin panel for creating users, assigning roles, disabling accounts, and resetting passwords
Audit Log: Persistent, searchable log of all mutations (who did what, when) with 365-day retention
Rate Limit Dashboard (v4.5+): New tab on the audit log page showing locked IPs, attempt counts, and a clear button
User-Scoped API Keys: API keys inherit the permissions of their owning user
Force Password Change: Temporary passwords trigger a mandatory change on first login
Smart End-User Search
Hybrid Search: Combines full-text exact matching with semantic vector search (Voyage AI embeddings), merged via reciprocal rank fusion
Configurable Ranking: All ranking weights editable in the admin panel — nav boost, title boost, boosted templates, demoted path prefixes, and penalty scores
Intelligent Defaults: Nav-linked pages surface first, concept-template pages rank above generic content, video transcripts are deprioritised
Title Boost: Pages where the query appears in the title always rank above body-only matches
Typeahead Suggestions: Fast prefix-matching suggestions — pages for direct navigation, keywords for full search — with the same structural ranking
Works Without Embeddings: Falls back to full-text search if no Voyage API key is configured
Rate Limiting: Per-IP and global rate limiting for DDoS protection
Developer & Integration
REST API: Full /api/v1/ JSON API with API key and OAuth token authentication, RBAC-enforced
OAuth 2.1: Authorization code flow with PKCE for remote MCP clients — no embedded passwords
CLI Tool: Command-line interface for all content management operations
URL Redirects: 301/302 redirect rules managed from the admin panel
Webhooks (v4.5+): HMAC-SHA256 signed event delivery for 6 event types (content.create, content.update, content.publish, content.unpublish, content.delete, and more); per-webhook secrets; delivery history with retry visibility; admin UI at /cm/webhooks. Webhook URLs must be publicly reachable: a URL that resolves to a loopback, private or link-local address is refused and logged as "blocked" (v7.4.3)
Cloudflare Integration (v4.5+): Auto-purge Cloudflare cache on publish/unpublish via Zone ID + API Token
Edge Caching Headers (v4.5+): ETag, Cache-Control, Last-Modified, Vary, and 304 Not Modified on all public pages
Structured JSON Logging (v4.5+): All server logs emit structured JSON with timestamp, level, message, and context fields
Site Customization
Theme Customization: Colors, fonts, border radius, custom CSS — all editable in the admin panel with version history
Header/Footer HTML: Full HTML control over site chrome injected around all pages
Asset Management: Upload and manage images, documents, and other files with path-based serving
Prerequisites
Go 1.24 or later
MongoDB Atlas account (free tier works great)
Quick Start
Clone the repository
Copy config.dev.json.example to config.dev.json
Edit config.dev.json with your MongoDB connection string
Edit with production values (use openssl rand -hex 32 for session_secret).
Installation
# Clone or navigate to the project
cd lightcms
# Install dependencies
go mod tidy
# Run the server
go run cmd/server/main.go
Or use the run script:
./run.sh
Configuration
LightCMS uses JSON config files. Create either:
config.dev.json - for development
config.prod.json - for production (takes precedence if both exist)
Field
Description
port
Server port (e.g., "8082" for dev, "80" for prod)
mongo_uri
MongoDB Atlas connection string
database_name
MongoDB database name. Optional, default lightcms
env
Environment: "development" or "production"
session_secret
Random string for session encryption
base_url
Public URL of the site
secure_cookies
true in production (HTTPS). false for local development over plain HTTP
When MONGO_URI is set, configuration comes from environment variables instead (MONGO_URI, SESSION_SECRET, BASE_URL, PORT, ENV, SECURE_COOKIES).
Database name. The server and the cmd/ tools use the database lightcms unless told otherwise. Set the DATABASE_NAME environment variable (it wins over database_name in the config file) to point an instance at another database on the same cluster, for example a staging or test copy. The server logs the database it connected to at startup.
Plain HTTP in development. With secure_cookies: false the admin works over http://localhost: cookies are not marked Secure and the CSRF origin check compares against http://. With secure_cookies: true (the production default) the admin must be reached over HTTPS; the CSRF check rejects plain-HTTP origins.
Note: Config files contain secrets and are excluded from git via .gitignore.
Log in at /cm/login with your email and password. On first startup with an empty database, LightCMS creates an admin account from the LIGHTCMS_ADMIN_EMAIL environment variable (defaults to admin@localhost with password admin123). Change your password immediately after logging in.
Select a template (Blog Post, Press Release, Explanatory Page, etc.)
Fill in the fields
Check "Published" and save
Managing Users (Admin Only)
Go to Users in the left sidebar (visible to admins only)
Create users with email, display name, and role (admin / editor / viewer)
Users receive a temporary password and are prompted to change it on first login
Disable accounts or reset passwords from the edit page
View a full audit trail of all user actions at Audit Log
Creating Custom Templates
Go to Templates → New Template
Define your fields (text, textarea, richtext, date, image, select)
Create an HTML layout using {{.field_name}} placeholders
Save the template
Available placeholders:
{{.title}} - Content title
{{.slug}} - URL slug
{{.published_at}} - Publication date
{{.your_field_name}} - Any custom field you define
Dynamic Index Pages: Tags, Snippets, and lc:query
LightCMS includes a system for building dynamic index pages that automatically update as you publish content. Three features work together: tags label individual pages, snippets define how each result is rendered, and lc:query directives embed live queries directly inside template layouts.
Tags
Tags are freeform string labels you attach to any content item. A page can have zero or many tags. They're the primary way to group content for querying.
Setting tags in the admin UI:
Open any content item in the editor
Find the Tags field (below the main fields)
Type a tag name and press Enter — repeat for multiple tags
Tags are exact-match strings. Capitalization and spaces are preserved — "AI & Machine Intelligence" and "ai & machine intelligence" are treated as different tags.
Snippets
A snippet is a named HTML template fragment stored in the CMS. When lc:query runs, it renders each matching content item through a snippet and concatenates the results.
Creating a snippet:
Go to Settings → Snippets in the admin panel
Click New Snippet, give it a name (e.g. glossary-pill)
Write HTML using Go template variables:
<a href="{{.FullPath}}">{{.Title}}</a>
Available variables inside a snippet:
Variable
Description
{{.Title}}
The content item's title
{{.FullPath}}
The public URL path (e.g. /my-page)
{{.Slug}}
URL slug only (e.g. my-page)
{{.MetaDescription}}
Meta description field
{{.PublishedAt}}
Publication timestamp
Example snippets:
A pill-style link (for glossary / tag cloud layouts):
An lc:query directive is an HTML comment you embed in a template layout. At page generation time — before the page is rendered — the CMS finds all matching content items, renders each one through the named snippet, and replaces the comment with the combined HTML.
Syntax:
Attributes:
Attribute
Required
Description
filter
Yes
Filter expression. Currently supports tag:TAGNAME to match content tagged with TAGNAME.
sort
No
Sort field and direction: title:asc, title:desc, created_at:asc, created_at:desc. Defaults to title:asc.
snippet
Yes
Name of the snippet to render each result through.
After the page is published, the directive is replaced with the rendered output of every published page tagged AI & Machine Intelligence, each passed through the glossary-pill snippet:
Important:lc:query directives must be placed in the template's HTML layout field, not inside content data fields. The CMS processes them during page generation before Go's template engine runs (which would otherwise strip HTML comments).
Automatic Regeneration
Index pages that use lc:query are automatically regenerated whenever:
A tagged content item is published or updated
The template layout is changed
The snippet is updated
Regenerate All is triggered manually from the admin panel
This means you never need to manually rebuild your index pages — publish a new concept page tagged "Games & Interactive Experiences" and it appears in every index that queries for that tag within seconds.
Complete Walkthrough: Building a Tagging-Powered Index
Here's how to build a concepts glossary that automatically stays up to date.
Step 1: Tag your concept pages
For each concept page, add the appropriate tag in the content editor. You can use as many tags as you like, and the same content item can appear in multiple index sections.
Step 2: Create a snippet
In Settings → Snippets, create a snippet named glossary-pill:
<a href="{{.FullPath}}">{{.Title}}</a>
Step 3: Create a template with lc:query sections
Create a new template (e.g. "Concepts Index") with this HTML layout:
<article class="index-page">
<h1>{{.title}}</h1>
<div class="page-content">
<h2>AI & Machine Intelligence</h2>
<div class="concept-links">
</div>
<h2>Games & Interactive Experiences</h2>
<div class="concept-links">
</div>
<h2>3D Graphics & Rendering</h2>
<div class="concept-links">
</div>
</div>
</article>
Note that {{.title}} is the Go template variable for the content item's title. Template variables use Go's {{.field}} syntax and are resolved after lc:query directives are expanded.
Step 4: Create and publish an index page
Create a new content item using your "Concepts Index" template. Give it a title and slug (e.g. /glossary). Publish it — the static page is generated with all the current tagged content already in place.
Step 5: Keep publishing
From now on, every time you create and publish a new concept page with a matching tag, all index pages that query for that tag are automatically regenerated and updated.
Template Variables
Beyond content data fields, templates have access to a few built-in variables:
Variable
Description
{{.title}}
The content item's title
{{.slug}}
URL slug
{{.published_at}}
Publication timestamp
{{.your_field}}
Any custom field defined in the template (richtext fields render as HTML)
Custom fields defined on your template are available directly by key. If you define a field with key intro, it's available as {{.intro}} in the layout. Richtext fields are automatically marked safe — their HTML is rendered as-is without escaping.
Content Authoring: Pre-Processing & Markup Features
LightCMS processes content field values before rendering them into your template. Authors can use the following markup features in any text or richtext data field.
Wikilinks
Link between pages using double-bracket syntax. Wikilinks are resolved at publish time and automatically kept up to date when a page's title or path changes.
Syntax
Result
[[Page Title]]
Link to a page matched by title (case-insensitive)
[[Page Title|display text]]
Same, with custom link text
[[/full/path]]
Link to a page by its exact URL path
[[/full/path|display text]]
Path link with custom link text
Broken links (no matching page found) render as <span class="broken-link">Page Title</span> so they are easy to identify and fix.
Snippet Includes
Embed a named snippet inline inside any content field:
[[include:snippet-name]]
The snippet-name must exactly match the Name field of a snippet in Settings → Snippets. Snippet includes are useful for reusable content blocks such as callouts, disclaimers, and calls to action that appear on many pages.
Table of Contents
Place {{.lc_toc}} anywhere in your template's HTML layout to inject an auto-generated table of contents at that position:
At page generation time, LightCMS scans all headings in the final rendered HTML and outputs a <nav class="lc-toc"> block with anchor links to each one. Headings automatically receive id= attributes derived from their text content (see Heading IDs below), so the TOC links work without any extra setup.
Heading IDs
All headings (<h1> through <h6>) in rendered page output automatically receive id= attributes derived from their text. This enables deep-linking to specific sections.
The id is generated by lowercasing the text and replacing spaces and punctuation with hyphens. If two headings produce the same id, a numeric suffix is appended (getting-started-2, etc.).
Markdown Field Type
Template fields can be given the type markdown instead of text or richtext. Markdown fields support GitHub Flavored Markdown (GFM) including tables, strikethrough, task lists, and autolinks. The field value is converted to HTML at page generation time.
Markdown fields are a good choice for structured content that benefits from simple markup without a WYSIWYG editor — documentation pages, changelogs, FAQs, and similar content.
To create a Markdown field, set the field type to markdown when defining the template:
Mention #tagname anywhere in a content field to automatically tag the page with that label. The tag is added to the page's tag list and participates in lc:query index pages just like manually applied tags.
Tag rules:
Must start with a letter
May contain letters, numbers, underscores, or hyphens
Example: This article covers #machine-learning and #ai adds both tags
This is a convenient alternative to editing the Tags field separately — useful when writing content in Markdown fields or richtext where you want to tag inline.
Creating Collections
Collections display grouped content (like a blog listing page).
Go to Collections → New Collection
Set the category filter to match your content's category
Define item and page templates
The collection will be available at /collection-slug
Customizing the Theme
Go to Theme in the admin panel
Adjust colors, fonts, and border radius
Add custom CSS if needed
Save to apply changes site-wide
End-User Search
LightCMS exposes a public search API at /api/search that your site's frontend can call.
Ranking weights are configurable in the admin panel under Tools → End User Search → Search Ranking. Defaults: title-match boost 0.20, nav-page boost 0.15, concept-template boost 0.05, video-path penalty −0.05. Configure your Voyage AI key under Configuration to enable semantic search.
Project Structure
lightcms/
├── cmd/
│ ├── server/main.go # HTTP server entry point
│ ├── mcp/main.go # MCP server entry point
│ ├── cli/main.go # CLI tool entry point
│ └── resetpw/main.go # Password reset utility
├── config/
│ └── config.go # Configuration loading
├── internal/
│ ├── apiclient/ # Reusable HTTP client for REST API
│ ├── auth/ # Authentication, RBAC permissions, session management
│ ├── cli/ # CLI subcommands and output formatting
│ ├── database/ # MongoDB connection & operations
│ ├── handlers/ # HTTP handlers (admin UI + REST API)
│ ├── mcp/ # MCP server and tool definitions
│ ├── middleware/ # API auth middleware (API keys + OAuth)
│ ├── models/ # Data models & default templates
│ ├── oauth/ # OAuth 2.1 authorization server
│ └── services/ # Business logic (content, search, users, audit, etc.)
├── static/ # CSS, JS, and uploaded files
├── content/ # Custom pages and generated HTML
└── .goreleaser.yaml # Release configuration
Fields: title, definition, topic_links — ideal for wiki-style knowledge base entries
Standard Page, Blank Page, Homepage
General-purpose layouts for flexible content.
Multi-User Access Control
LightCMS v2.0+ supports multiple users with role-based permissions.
Roles
Role
Capabilities
admin
Full access: manage users, templates, theme, settings, audit log, all API keys
editor
Create/edit/delete/publish content; upload and delete assets; manage own API keys
viewer
Read-only access to content, templates, assets, and settings
Audit Log
Every mutation (content create/update/delete/publish, user management, settings changes, logins) is logged with the acting user's email, timestamp, and relevant details. Logs are retained for 365 days and accessible at /cm/audit.
API Key Permissions
API keys created by a user inherit that user's role. A key created by an editor cannot perform admin-only operations even if its token is shared. Admins can manage all keys; non-admins can only manage their own.
First-Time Migration
On first startup with an empty users collection, LightCMS automatically creates an admin user from the existing password hash in the database. Set the LIGHTCMS_ADMIN_EMAIL environment variable to specify which email address to use (defaults to admin@localhost).
API Keys
API keys are required for the REST API, MCP server, and CLI tool. Create them from the admin panel.
Log in at /cm
Go to Settings → API Keys
Click Create New Key, give it a name and description
Copy the key immediately — it's only shown once
Keys use the format lc_ followed by 32 hex characters. They're stored as SHA-256 hashes and inherit the permissions of the creating user.
OAuth 2.1 Authorization
LightCMS implements OAuth 2.1 so that remote MCP clients (like Claude's Cowork) can securely connect without embedding passwords or API keys. This follows the standard authorization code flow with PKCE.
Endpoints
Endpoint
Purpose
POST /oauth/register
Dynamic client registration (RFC 7591)
GET /oauth/authorize
Authorization page (admin login + consent)
POST /oauth/token
Token exchange and refresh
POST /oauth/revoke
Token revocation (RFC 7009)
GET /oauth/jwks
JWKS endpoint (opaque tokens, returns empty)
Security
PKCE (S256) required for all authorization requests
Token rotation: refresh tokens are single-use; a new pair is issued each time
Short-lived access tokens: 1-hour TTL
Refresh tokens: 30-day TTL, revocable
Rate limiting: failed login attempts trigger progressive lockouts (1 min → 5 min → 15 min)
All tokens stored as SHA-256 hashes in the database
How Clients Connect
Client fetches /.well-known/oauth-authorization-server to discover endpoints
Client calls POST /oauth/register with its name and redirect URI
Client redirects admin to /oauth/authorize with PKCE challenge
Admin enters password and approves access
Client exchanges the authorization code for access + refresh tokens
Client uses the access token as a Bearer token on /mcp or /api/v1/ endpoints
This is all handled automatically by MCP-compatible clients — you just provide your LightCMS URL and approve the connection.
REST API
LightCMS provides a full REST API at /api/v1/ authenticated with API keys or OAuth tokens. All endpoints enforce RBAC — the permissions of the authenticated user (or key owner) determine what's allowed.
Authentication
Include an API key or OAuth access token in the Authorization header:
# With API key
curl -H "Authorization: Bearer lc_your_key_here" http://localhost:8082/api/v1/content
# With OAuth token
curl -H "Authorization: Bearer <oauth_access_token>" http://localhost:8082/api/v1/content
Endpoints
Resource
Endpoints
Content
GET/POST /content, GET/PUT/DELETE /content/{id}, POST .../publish, .../unpublish, .../restore, GET .../versions, POST .../versions/{v}/revert, GET /content/by-path?path=...
lightcms content list # List all content
lightcms content get <id> # Get content by ID
lightcms content create --template <id> --title "My Post" --slug my-post --data '{"body":"Hello"}'
lightcms content publish <id> # Publish content
lightcms content versions <id> # Show version history
lightcms template list # List templates
lightcms asset upload --file logo.png --path /images/logo.png
lightcms theme update --primary-color "#1a1a2e"
lightcms search "search terms" # Search content
lightcms api-key create --name "CI/CD" # Create API key
lightcms --json content list # JSON output
Run lightcms --help for full usage.
MCP Server (AI-Powered Content Management)
LightCMS includes a full MCP (Model Context Protocol) server with 130 tools and 3 prompt resources for managing your entire website through AI agents. It supports two transport modes:
Stdio — for local tools like Claude Code
HTTP Streamable — for remote/sandboxed clients like Claude's Cowork, Claude Desktop, or any MCP-compatible app
Option A: Local Setup (Claude Code via Stdio)
Best for developers using Claude Code directly on the same machine.
Create an API key in the admin panel at /cm → Settings → API Keys
go build -o bin/lightcms-mcp ./cmd/mcp
claude mcp add --transport stdio lightcms-mcp \
-e LIGHTCMS_URL="http://localhost:8082" \
-e LIGHTCMS_API_KEY="lc_your_key_here" \
-- /path/to/lightcms/bin/lightcms-mcp
Restart Claude Code and run /mcp to verify.
Option B: Remote Setup (Cowork / Claude Desktop via HTTP + OAuth)
Best for sandboxed desktop apps that can't run local binaries. The HTTP MCP endpoint at /mcp supports OAuth 2.1 authorization — no API keys or passwords need to be embedded in the client.
How it works:
The client discovers your LightCMS instance via well-known endpoints
It registers as an OAuth client (one-time, automatic)
You authorize the client by entering your admin password in the browser
The client receives short-lived access tokens and refreshes them automatically
To connect from a remote MCP client, just provide your LightCMS URL (e.g., https://yoursite.example.com). The client handles the rest using standard OAuth 2.1 discovery.
Discovery endpoints:
Endpoint
Purpose
/.well-known/oauth-authorization-server
OAuth server metadata (RFC 8414)
/.well-known/oauth-protected-resource
Protected resource metadata (RFC 9728)
/.well-known/mcp/server-card.json
MCP server card with tool schemas
Authentication
The MCP HTTP endpoint accepts both authentication methods:
API keys (lc_ prefix) — long-lived, created in admin panel
OAuth 2.1 tokens — short-lived, obtained through the authorization flow
Both methods enforce RBAC based on the authenticated user's role.
LIGHTCMS_URL — Server URL (default: http://localhost:8082)
LIGHTCMS_API_KEY — API key (required for stdio mode)
MCP Examples
These examples show how the MCP tools work together to manage a website through natural language. Each example lists the user prompt and the exact MCP tool calls that execute behind the scenes.
Example 1: Create and Publish a Blog Post
Prompt: "Create a blog post about AI agents and publish it"
Tool calls:
list_templates — finds the Blog Post template and its ID
create_content — creates the post with template ID, title, slug, and field data:
{
"template_id": "6971098ad0761968133b8e43",
"title": "The Rise of AI Agents",
"slug": "rise-of-ai-agents",
"data": {
"excerpt": "How autonomous AI agents are reshaping software development.",
"content": "<p>AI agents represent a fundamental shift...</p>",
"author": "Editorial Team"
}
}
publish_content — makes it live; a static HTML page is generated at /rise-of-ai-agents
Example 2: Update the Site Theme
Prompt: "Change the site colors to a dark theme with blue accents"
Tool calls:
get_theme — reads current theme settings (colors, fonts, header/footer HTML)
create_content — creates the index page using the new template:
{
"template_id": "<concepts-index-template-id>",
"title": "Concepts Glossary",
"slug": "glossary",
"data": {
"intro": "An index of all concepts, grouped by category."
}
}
update_content — tags several existing concept pages (each call):
{ "tags": ["AI & Machine Intelligence"] }
publish_content — publishes the index page; the lc:query directives are resolved at this moment and the page is generated with all currently-tagged content already populated.
From now on, every time a new concept page is published with a matching tag, the index page at /glossary is automatically regenerated — no further action needed.
Example 11: Full-Text Search and Content Audit
Prompt: "Find all pages that mention 'pricing' and show me which ones are still in draft"
Tool calls:
search_content — performs a full-text search across all content fields:
{ "query": "pricing", "search_type": "fulltext" }
Returns matching content items with their publish status, paths, and which fields matched:
Found 4 results for 'pricing':
- "Pricing Plans" at /pricing — published — matched in: content
- "Enterprise FAQ" at /enterprise-faq — published — matched in: content, sidebar
- "New Pricing Draft" at /new-pricing — draft — matched in: title, content
- "Q1 Press Release" at /press/q1-update — draft — matched in: body
The two draft items can then be reviewed, edited, and published as needed.
Example 12: Bulk Content Migration
Prompt: "Add a 'last_reviewed' field to every page in our /docs section and publish them all"
Tool calls:
list_content — fetches all content under /docs with full field data in one call:
{ "folder_path": "/docs", "include_data": true }
Returns IDs, titles, current field values, and publish status for all 34 pages.
(parallel) Agent fans out into batches of 50 and calls bulk_update_content concurrently:
A floating preview bar is injected into the live site — visiting it with the fork cookie active shows both pages exactly as they'll look after merge.
merge_fork — after approval, merges both fork pages into live content and regenerates their static HTML:
{ "fork_id": "fork_abc123" }
Returns a summary of merged pages (counts plus created_ids and updated_ids) and any conflicts detected. Pages the fork adds are created as drafts unless you pass "publish_new": true; pages on hold always stay drafts. The fork's page copies are deleted once the merge succeeds.
Example 14: Site-Wide Notice with Auto-Republish
Prompt: "Prepend a deprecation notice to all pages in our /v1 docs section and republish them"
Tool calls:
bulk_field_operation — appends the notice to a specific field across the entire folder in one call:
Returns counts of updated and republished pages. The live site reflects the change immediately.
If the notice ever needs to be removed, a single scoped_search_replace_execute with the exact notice HTML reverts all pages in one call.
Working with Snippets
# List all snippets
list_snippets
# Create a callout snippet
create_snippet {
"name": "callout-warning",
"description": "Warning callout box",
"html": "<div class=\"callout callout-warning\"><strong>⚠️ {{.Title}}</strong><p>{{.Body}}</p></div>"
}
# Use a snippet inline in content
update_content {
"id": "...",
"data": {
"body": "Here is important information:\n\n[[include:callout-warning]]\n\nContinued text..."
}
}
Content Tagging & Index Pages
# Tag a page at creation time
create_content {
"template_id": "...",
"title": "Introduction to AI",
"slug": "intro-to-ai",
"tags": ["AI & Machine Intelligence", "Getting Started"],
"data": { "body": "..." }
}
# Inline tagging via content body
update_content {
"id": "...",
"data": {
"body": "This page covers #machine-learning and #neural-networks."
}
}
# Query directive in a template layout (for index pages)
Bulk Operations
# Step 1: Export all Concept Pages with specific fields
export_content {
"template_name": "Concept Page",
"fields": ["definition", "layer_badge"]
}
# Step 2: Transform the data externally, then bulk update
bulk_update_content {
"updates": [
{ "id": "abc123", "data": { "layer_badge": "<new html>" } },
{ "id": "def456", "data": { "layer_badge": "<new html>" } }
],
"version_comment": "Updated layer badges"
}
# Clear a field across all pages of a template
bulk_field_operation {
"operation": "clear",
"field": "old_badge",
"template_name": "Concept Page",
"version_comment": "Cleared deprecated field"
}
# Prepend a disclaimer to all blog posts
bulk_field_operation {
"operation": "prepend",
"field": "body",
"value": "<div class=\"disclaimer\">Views are my own.</div>",
"template_name": "Blog Post",
"version_comment": "Added disclaimer to all posts"
}
Regex Search & Replace
# Preview: find all pages with old badge HTML pattern
scoped_search_replace_preview {
"search": "<div class=\"badge-v1\".*?</div>",
"replace": "",
"regex": true,
"template_name": "Concept Page"
}
# Execute after confirming preview
scoped_search_replace_execute {
"search": "<div class=\"badge-v1\".*?</div>",
"replace": "",
"regex": true,
"template_name": "Concept Page",
"version_comment": "Removed old v1 badge HTML"
}
Wikilinks
# Link to another page by title
update_content {
"id": "...",
"data": {
"body": "See also: [[Machine Learning]] and [[AI Ethics|ethics considerations]]."
}
}
# Find what pages link to a given path
get_backlinks { "path": "/concepts/machine-learning" }
Content Versioning
# See version history for a page
get_content_versions { "content_id": "abc123" }
# Restore a previous version
revert_to_version {
"content_id": "abc123",
"version": 3,
"version_comment": "Reverted to pre-redesign version"
}
Development
# Run with hot reload (using air)
go install github.com/cosmtrek/air@latest
air
# Build all binaries
go build -o bin/lightcms-server ./cmd/server
go build -o bin/lightcms-mcp ./cmd/mcp
go build -o bin/lightcms ./cmd/cli
# Run the server
./bin/lightcms-server
Security Notes
For production:
Use a strong session_secret — minimum 32 characters (generate with openssl rand -hex 32). The server hard-fails on startup if this requirement isn't met in production.
Set LIGHTCMS_ADMIN_EMAIL so the initial admin account uses your real email
Change the default admin password immediately after first login
Use HTTPS (put behind a reverse proxy like nginx or caddy)
Restrict MongoDB Atlas IP whitelist to your server IPs
API keys inherit the permissions of their owning user — keep admin keys secure
Review the audit log regularly at /cm/audit
Regularly backup your MongoDB database
Configure max_upload_bytes in site settings to cap file upload size for your use case
Security features built in:
CSRF protection on all /cm routes
Admin Content-Security-Policy: scripts and stylesheets load from the site itself only (the editor's Quill files are vendored, not fetched from a CDN)
RBAC permission checks on all admin handlers and REST API endpoints
Session cookies: SameSite=Strict, 24-hour expiry, Secure in production
Audit logging on all mutations with 365-day retention
Fly.io deployments: Fly-Client-IP header used for real client IP (unspoofable, unlike X-Forwarded-For)
Chat widget prompt injection defense: user input wrapped in XML delimiters, </ sequences escaped
Privacy Policy
LightCMS is self-hosted software — you control your database, your hosting, and your data. The MCP server and CLI tool connect to your LightCMS instance via the REST API — no data is transmitted to Metavert LLC or any third party.