Lightcms MCP Server

AI-native CMS with 41 MCP tools for managing websites through natural language.

Remote serverstreamable-httpGo

What is the Lightcms MCP server?

Lightcms MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. AI-native CMS with 41 MCP tools for managing websites through natural language.

What you get

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.

  • MCP Integration — Full Model Context Protocol server with 106 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

What the assistant can call

Once Lightcms is connected, these are the calls the assistant has available:

  • 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
  • Snippets — A snippet is a named HTML template fragment stored in the CMS. When lc:query runs, it r

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

  • Go 1.24 or later - MongoDB Atlas account (free tier works great)

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Lightcms's toolset — Tags, Snippets — is a fair guide to whether it matches your workflow. It is maintained by jonradoff; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Lightcms's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the lightcms mcp server does with a few real requests.

Available tools

ToolWhat it does
TagsTags 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.
SnippetsA snippet is a named HTML template fragment stored in the CMS. When lc:query runs, it r

Configuration

  • Go 1.24 or later - MongoDB Atlas account (free tier works great)

Example prompts to try

  • Use Lightcms to Tags.
  • Use Lightcms to Snippets.

Frequently asked questions

It connects Lightcms to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Tags, Snippets) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Lightcms directly.