A
licenseNot graded
qualityD
maintenanceUnofficial MCP server for Ghost CMS that enables managing posts, pages, tags, and images through any MCP-compatible client.
MIT
Ghost Publisher MCP
Related Servers
Alternatives to Ghost Publisher MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePrivate MCP server for validating, previewing, creating, and updating Substack newsletter drafts through an MCP-compatible client.218 npm1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for managing Ghost blogs from AI coding editors. Create, edit, publish, and sync blog posts directly from tools like Claude Code or Cursor.13 npm1MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for publishing markdown articles to Medium and Substack via unofficial APIs, with tools to list, create, and manage posts and drafts.-
- AlicenseAqualityAmaintenanceMCP server for Substack — read posts, manage drafts, and upload images. Safe by design: cannot publish or delete.25809 npm35MIT
- AlicenseBqualityBmaintenanceOpen-source MCP server that turns any CMS backend into an AI-agent-ready content management system. It provides tools for content CRUD, idea management, and publication tracking, with safety features requiring human approval for publishing.52MIT
TDQS
A3.6/5.0
Scored across 24 tools
Disambiguation4/5
Tools are mostly well-bounded by resource and action (posts vs. pages, draft vs. publish vs. schedule). The main risk is the cluster of checking tools (check_connection, check_site_health, check_live_posts, check_live_pages, audit_content), but their descriptions distinguish scope and side effects well enough.
Naming Consistency5/5
All tool names use snake_case with a consistent verb_noun or verb form (list_posts, get_page, publish_pages, schedule_posts, check_live_pages). There are no mixed conventions or confusing abbreviations.
Tool Count3/5
With 24 tools, the set is on the heavy side for a Ghost publishing server. Many post/page pairs (publish_posts/publish_pages, unpublish_posts/unpublish_pages, list_posts/list_pages) could be parameterized, though the domain is complex enough that most tools earn a place.
Completeness4/5
The surface covers the core publishing lifecycle: list/get, create drafts, edit via change sets, publish/unpublish, schedule/unschedule posts, upload images, deploy, and live verification. Minor gaps remain, such as no delete operation and no write access for tags or authors, but these are workable around for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo issues