A
licenseB
qualityA
maintenanceEnables AI assistants to publish and manage blog posts on Misar.Blog, including drafts, series, AI content generation, and analytics.
26
469 npm
1
MIT
cmskite-mcp
by devicorn
Related Servers
Alternatives to cmskite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to manage a blog directly from an IDE, including drafting, editing, publishing, scheduling, SEO optimization, and analytics tracking through natural language.6,688,793 npmBSD 3-Clause
@micropage-sh/mcpofficial
AlicenseAqualityAmaintenanceEnables AI assistants to create, edit, and publish micropages and posts from markup, with optional controls for subscriber emails, project deletion, and form submissions.20281 npm4MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with WordPress blog systems for automated content management and publishing via the WordPress REST API.5 npm1MIT
- AlicenseNot gradedqualityBmaintenanceLets AI assistants manage a self-hosted content hub: create, edit, publish, and update articles across nine platforms, refresh account article lists, and sync changes through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage VergeCMS blogs through natural language, providing complete CRUD operations for blogs and articles with secure browser-based authentication and automatic token persistence.MIT
TDQS
A3.6/5.0
Scored across 27 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, with resource+action pairs that do not overlap. Even potentially similar tools like get_project vs get_project_summary, list_posts vs search_posts, and get_content_analytics vs get_post_analytics are explicitly differentiated in their descriptions. No ambiguity that would cause misselection.
Naming Consistency4/5
Almost every tool follows a consistent snake_case verb_noun pattern (list_projects, create_post, update_category, delete_post, etc.). The single outlier is whoami, which breaks the pattern but is a widely understood command. Overall highly predictable with one minor deviation.
Tool Count4/5
27 tools is on the heavy side, but the server covers a broad domain (projects, categories, tags, authors, posts, API keys, integration, analytics), so each tool earns its place. The count is slightly over the ideal 3-15 range but reasonable for the scope.
Completeness3/5
Posts have full CRUD, and categories have list/create/update/delete, but several resources lack lifecycle operations: tags and authors have only list/create (no update/delete), projects lack delete, API keys lack revoke/delete, and workspaces lack delete. These are notable gaps for a CMS agent, though core content workflows are covered.
Maintenance
ActivityMaintained
ResponsivenessNo issues