Local credentials
The Ghost Admin key stays in the local MCP client configuration instead of a Ghost Publisher-hosted service.
Ghost CMS MCP server
Ghost Publisher is an unofficial, local-first MCP server for Ghost posts and Pages, publication diagnostics, scheduling, images, separately approved publishing, deploy hooks, and bounded live checks.
One-command setup
The installer prompts privately for a Ghost Admin API key, checks the connection without writing, and asks before changing supported client configuration.
npx -y ghost-publisher-mcp@latest setup \
--url https://your-ghost.example.comSafer first connection: select the read-only permission profile, then grant only the workflow you need.
Why use it
The Ghost Admin key stays in the local MCP client configuration instead of a Ghost Publisher-hosted service.
Work with posts, Pages, images, schedules, diagnostics, deploy hooks, and live checks—not the full Ghost Admin API.
Revision checks, signed previews, exact scopes, and caller-attested confirmation guard approved edits and transitions.
Publish an approved batch, trigger one configured deployment, and check the rendered public result as separate bounded steps.
Workflow
Permission profiles
Install free
You need Node.js 22 or newer, a Ghost site, and a Ghost custom integration Admin API key. The interactive installer detects Codex, Cursor, and Claude Desktop configuration targets.
npx -y ghost-publisher-mcp@latest setup \
--url https://your-ghost.example.com# Preview configuration without changing it
npx -y ghost-publisher-mcp@latest setup \
--url https://your-ghost.example.com \
--permission read-only \
--dry-runNever paste the Admin key into a chat, issue, command argument, commit, screenshot, or hosted form.
Verified proof
The Ortak Alan case study records the maintainer-operated setup, exact versions, read-only verification, and operational limits. It does not claim that this MCP alone caused search growth.
Questions
No. It is an independent open-source project maintained by BlogFactoryHQ and is not affiliated with or endorsed by the Ghost Foundation.
Yes, when the publisher profile is enabled and the caller separately confirms the exact transition. Draft creation itself can never publish.
No. Deletion, members, newsletters, themes, users, roles, arbitrary queries, and general site administration are outside the tool surface.
It stays in the selected MCP client's local user configuration or process environment. Ghost Publisher does not operate a hosted credential service.
Yes. It has separate bounded Page workflows plus optional deploy hooks and public URL templates for headless or static delivery checks.
The installer supports Codex, Cursor, and Claude Desktop configuration targets. The server uses local stdio and can be configured manually in compatible MCP clients.
No. Your AI client writes or researches with its own capabilities. Ghost Publisher performs the Ghost-specific actions and stores no AI billing state.
Run the installer privately, verify the site without writing, and grant only the workflow you are ready to approve.
Install free