A
licenseNot graded
qualityC
maintenanceEnables AI assistants to securely manage Ghost CMS blogs, including posts, pages, members, newsletters, tiers, and more via natural language.
1,974 npm
MIT
ghost-mcp
by seagyn
Related Servers
Alternatives to ghost-mcp
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseAqualityCmaintenanceEnables AI models to manage, curate, draft, publish, and administer self-hosted Ghost CMS blogs and newsletters.346 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.6 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with Ghost CMS through the Ghost Admin API via LLM interfaces. It provides comprehensive tools for managing posts, members, newsletters, and other site entities through secure JWT authentication.-
- 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.6 npm1MIT
TDQS
D1.6/5.0
Scored across 36 tools
Disambiguation3/5
Resource prefixes (tiers, offers, posts, etc.) are distinct, but the absence of descriptions makes browse vs read and draft vs non-draft actions ambiguous. Members vs users also have unclear boundaries, and overlapping action names across resources compound the issue.
Naming Consistency5/5
All tools follow a consistent snake_case pattern of [plural_resource]_[action] (e.g., tiers_read, posts_add). The draft subresource pattern (posts_draft_add) is also applied uniformly, and action verbs (browse, read, add, edit) are reused predictably.
Tool Count2/5
At 36 tools, the set is heavy for the apparent scope, even though it covers nine resources. Many tools are repetitive action variants that could be consolidated, and the lack of descriptions makes the large surface harder to navigate.
Completeness2/5
Core CRUD is incomplete: no delete operations exist for any resource, and posts/pages have draft creation/editing but no publish, unpublish, or schedule actions. Media handling, settings, and other common CMS lifecycle operations are also absent, causing significant gaps for agent workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues