Lightcms vs Lhremote — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Lightcms vs Lhremote
In-depth architectural comparison of the Lightcms and Lhremote MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Lightcms
Marketing · Local stdio
Quality: 47/100 (Fair) | Auth: other
Lhremote
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Lightcms if you need specialized Marketing tools running via a local process. Choose Lhremote if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Lightcms when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: MCP tools for website content management, Local stdio and HTTP streamable transports, Content versioning, diffs, revert, and soft delete.
AI-native CMS with 72 MCP tools for managing websites through natural language. Create and publish content, manage templates, assets, snippets, themes, collections, redirects, and multi-site forks — with full content versioning and semantic search.
Open-source CLI and MCP server for LinkedHelper automation — 32 tools for campaign management, messaging, and profile queries via Chrome DevTools Protocol.
Category & Scope
Tools & Capabilities Breakdown
Lightcms Tools (6)
MCP tools for website content management
Local stdio and HTTP streamable transports
Content versioning, diffs, revert, and soft delete
Bulk imports with job tracking
Approval workflows and agent sandboxes
Semantic search with optional Ollama embeddings
Lhremote Tools (69)
find-app
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Lightcms is categorized under Marketing and uses a local stdio subprocess. In contrast, Lhremote belongs to Marketing using local stdio subprocess. Select Lightcms when you need capabilities focused on marketing and Lhremote when you require tools for marketing.