A
licenseB
qualityD
maintenanceLightweight content management system for websites, built for the AI era
72
31
MIT
mini-cms-mcp
by paycodero
Related Servers
Alternatives to mini-cms-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceOpen-source MCP server that turns any CMS backend into an AI-agent-ready content management system. It provides tools for content CRUD, idea management, and publication tracking, with safety features requiring human approval for publishing.52MIT
NextBlock CMSofficial
FlicenseNot gradedqualityAmaintenanceOpen-source Next.js + Supabase CMS with a per-site MCP server for building and editing sites from any agent23-- AlicenseNot gradedqualityCmaintenanceMCP server for WordPress content management via REST API, supporting posts, pages, media, comments, and terms through natural language interfaces like Cursor, ChatGPT, Codex, and Claude.14 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP-native CMS that lets you create and edit content by chatting, with typed schemas and seamless publishing.7 npm3MIT
- FlicenseNot gradedqualityCmaintenanceTurns structured content from a CMS into a static MCP server, enabling AI agents to access content via auto-generated tools without a database or runtime dependencies.-
TDQS
A3.8/5.0
Scored across 26 tools
Disambiguation4/5
Most tools are clearly separated by resource and action, and the descriptions are specific enough to guide an agent. The main risk is the delete/unpublish family (sterge, retrage, sterge_imagine, sterge_fisier), which can look similar at a glance but is differentiated in the descriptions.
Naming Consistency3/5
All names are lowercase snake_case, which helps readability, but they mix conventions: many are bare verbs (listeaza, citeste, sterge), others are verb_noun (sterge_imagine, urca_fisier), and a few are noun phrases (despre_site, pagini_de_pornire, link_urcare). This is still understandable but not a consistent predictable pattern.
Tool Count2/5
At 26 tools, the server sits above the 25+ threshold and is heavy even for a mini-CMS with media, files, redirects, and connection management. The number of choices increases the chance of mis-selection and would benefit from consolidation.
Completeness5/5
The set covers the full lifecycle for the main content resources: save, read, list, search, publish, retract, delete, restore, preview, versions, redirects, media, files, export, and connection management. There are no evident dead ends in the described domain.
Maintenance
ActivityMaintained
ResponsivenessNo issues