Ghost CMS MCP Server
Related Servers
Alternatives to Ghost CMS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely manage Ghost CMS blogs, including posts, pages, members, newsletters, tiers, and more via natural language.3,849 npmMIT
- AlicenseAqualityCmaintenanceEnables AI models to manage, curate, draft, publish, and administer self-hosted Ghost CMS blogs and newsletters.3414 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables to manage Ghost CMS instance using LLM interfaces. Supports comprehensive CRUD operations on posts, members, newsletters, offers, tags, tiers, users, and webhooks.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Ghost CMS instances through the Admin API, supporting content operations (posts, tags), member management, newsletters, tiers, offers, and webhooks through natural language interactions.10 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Ghost CMS content including posts, members, users, tags, tiers, offers, newsletters, invites, roles, and webhooks via the Ghost Admin API.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Ghost CMS sites through both Content (read-only) and Admin (read/write) APIs, allowing natural language management of posts, pages, tags, and settings.1MIT
TDQS
Scored across 10 tools
Most tools map to distinct actions on posts (list, get, create, update, delete, publish, unpublish, bulk variants). The only minor overlap is between list_posts and search_posts, since both retrieve posts and list supports filters. Overall boundaries are clear enough for reliable selection.
All tools follow a strict ghost_posts_<verb> snake_case pattern. The verbs are conventional and predictable, with bulk operations clearly marked. No naming inconsistencies.
Ten tools is well-scoped for post management, covering CRUD plus publish lifecycle and bulk operations. Each tool earns its place without redundancy.
Post lifecycle coverage is excellent: list, get, create, update, delete, publish, unpublish, search, and bulk operations. However, as a Ghost CMS server it omits adjacent resources like pages, tags, authors, and media, which limits broader CMS workflows.