A
licenseNot graded
qualityD
maintenanceEnables 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.
1
MIT
Ghost Styling MCP
Related Servers
Alternatives to Ghost Styling MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates with the Ghost Admin API to allow programmatic management of Ghost CMS features, including posts, pages, tags, authors, members, and image uploads, providing efficient content management capabilities.6 npm3MIT
- AlicenseAqualityCmaintenanceEnables AI models to manage, curate, draft, publish, and administer self-hosted Ghost CMS blogs and newsletters.346 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.11 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely manage Ghost CMS blogs, including posts, pages, members, newsletters, tiers, and more via natural language.1,287 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Ghost CMS content including posts, members, users, tags, tiers, offers, newsletters, invites, roles, and webhooks via the Ghost Admin API.-
TDQS
A3.6/5.0
Scored across 55 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, with detailed descriptions that prevent confusion between similar operations (e.g., publish_post vs update_post, create_theme vs upload_theme vs activate_theme). The boundaries between content types (post/page/member/newsletter) are well-defined.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern (e.g., create_post, list_members, update_theme). Even longer names like upload_image_from_url adhere to the same scheme. No mixing of casing or irregular verbs.
Tool Count2/5
55 tools is excessive for a single MCP server, especially one focused on 'Styling'. The server includes full CRUD for many Ghost entities (members, offers, newsletters, etc.) well beyond styling, making the surface overwhelming and the scope unfocused.
Completeness4/5
The tool set covers the full styling workflow (extract brand → create/restyle/preview/upload/activate theme) and basic CRUD for most content types. Minor gaps exist (no delete_theme, delete_newsletter only via archive, no user management) but these are often API limitations.
Maintenance
ActivityStale
ResponsivenessNo issues