velocms-mcp
Related Servers
Alternatives to velocms-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for publishing to WordPress. 13 tools cover posts, categories, tags, image hosting, featured images, and SEO metadata (Rank Math, etc.) One call runs the full markdown-to-live-URL pipeline.135 npm4AGPL 3.0
- FlicenseNot gradedqualityCmaintenanceMCP wrapper over the dustinedwards.info operator publish API, exposing five tools for managing blog posts (list, get, save, sync, delete) while containing no policy of its own.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse Velog posts, safely create drafts and private posts, validate Markdown, and maintain a local searchable Markdown archive.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to manage Google Blogger blogs via the Blogger API v3, including listing and searching posts, creating drafts, editing, publishing or scheduling posts, managing static pages, and moderating comments.18MIT
- AlicenseAqualityAmaintenanceRun all of WordPress + SEO, Security, WooCommerce Shop & Elementor: 10 websites in one connector. Posts, pages, media, comments and updates from Claude, ChatGPT or Cursor. Start free.95GPL 2.0
- AlicenseAqualityCmaintenanceAn MCP server for managing Google Blogger blogs, posts, pages, comments, and media via the Blogger API v3. Includes OAuth authentication, Base64 image embedding, and lightweight listing modes.2924 npmMIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action: post CRUD, publish state transitions, media listing, comment moderation, member listing, and site settings retrieval. No two tools overlap in purpose.
All tools follow a consistent snake_case verb_noun pattern (get_, create_, list_, update_, delete_, publish_, unpublish_, moderate_). The consistent use of singular/plural nouns is conventional and readable.
12 tools is well-scoped for a CMS. Post lifecycle is fully represented, and the addition of media, comments, members, and settings covers the main auxiliary resources without unnecessary bloat.
Post CRUD and publishing workflow are complete, but media only supports listing, site settings only get, and comments lack deletion. These read-only surfaces create dead ends for agents trying to manage those resources.