ghost-mcp
Provides tools for managing a Ghost CMS site, including browsing and reading posts, pages, tags, tiers, newsletters, offers, members, and users, plus writing and editing content with draft-scoped options that cannot publish.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ghost-mcp Write a draft post about our Q3 roadmap"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ghost-mcp (hardened fork)
A Model Context Protocol server for Ghost CMS. This is a fork of MFYDev/ghost-mcp that removes the tools which are dangerous to hand to a language model, adds coverage for pages, and adds draft-scoped write tools that cannot publish.
Why this fork exists
A Ghost Admin API key cannot be scoped. There is no read-only mode, no per-resource restriction, and no short-lived token. An integration key is all-or-nothing, so the only place the capability surface can be reduced is at tool registration, before the model ever sees a tool exists.
Upstream registers every verb the Ghost client offers. That includes creating webhooks pointing at arbitrary URLs, which is a persistent exfiltration channel that outlives the server being uninstalled, and unconfirmed deletes on every resource. This fork refuses those.
Related MCP server: Ghost MCP
What is refused
src/policy.ts holds a deny-list enforced by a Proxy over McpServer.tool().
Denied names are never registered, so they do not appear in tools/list and
cannot be called even if the model is talked into trying.
Refused | Reason |
|
|
| Privilege-granting. |
| Irreversible, and offered with no confirmation step. |
Most of those are not reachable with an integration key anyway, so refusing
them costs almost no real capability. The four that were genuinely callable are
posts_delete, tags_delete and the three webhook tools.
There is deliberately no theme upload tool. POST /admin/themes/upload is open
to integration keys and a theme is a ZIP that can carry front-end JavaScript for
the public site. If an upstream merge ever adds one, it belongs in the
deny-list, not in the tool list.
What is added
Pages. Upstream has no pages_* tools at all, so standalone pages such as
About or Contact were unreachable while posts were fully covered. pages_browse,
pages_read, pages_add and pages_edit mirror the posts module.
Draft-scoped write tools. posts_add and posts_edit are full-power:
status is settable so they can publish, and edit can overwrite a published
post. Those are worth gating behind human approval, which makes a drafting loop
tedious. So there are narrower tools that are safe by construction:
posts_draft_add,pages_draft_addforcestatus: "draft". It is not a parameter, so publishing is not expressible in the schema the model sees.posts_draft_edit,pages_draft_editread the target first and refuse if it is not a draft, so published content cannot be overwritten. They also resolveupdated_atthemselves, so a stale value cannot trigger Ghost's collision error and the caller does not need a separate read.
That split is the point: approve the narrow tools freely, keep the powerful ones behind a prompt.
Tools
Read: posts_browse, posts_read, pages_browse, pages_read, tags_browse,
tags_read, tiers_browse, tiers_read, newsletters_browse,
newsletters_read, offers_browse, offers_read, members_browse,
members_read, users_browse, users_read, roles_browse, roles_read.
Write: posts_draft_add, posts_draft_edit, pages_draft_add,
pages_draft_edit, posts_add, posts_edit, pages_add, pages_edit,
tags_add, tags_edit, tiers_add, tiers_edit, newsletters_add,
newsletters_edit, offers_add, offers_edit, members_add, members_edit.
members_browse and members_read return unmasked subscriber data, including
email addresses and Stripe customer identifiers. Treat them as a separate
approval tier from the rest of the read tools.
Running it
Build, then run build/server.js over stdio with three environment variables:
GHOST_API_URL=https://yoursite.ghost.io
GHOST_ADMIN_API_KEY=<id>:<secret>
GHOST_API_VERSION=v5.0GHOST_API_VERSION must be a v5.x value even on a Ghost 6 site. The Ghost
client maps v5 and v5.x to the unversioned /admin/ path, but any other
v{major}.{minor} to /v{major}/admin/, a versioned path Ghost removed in v5.
Setting v6.0 makes every request return 404. The real version is negotiated
through the Accept-Version header.
Do not put the key in your MCP client's config file. Config files get committed,
and a key passed inside a shell command string is visible to ps for every
process on the machine. Fetch it in a launcher script instead, so it reaches the
server through the environment and never through a command line.
Tests
npm testscripts/check-denied-tools.mjs starts the real server, asks it over MCP what it
exposes, and fails if anything matching _delete$, ^webhooks_, ^invites_,
^themes_ or ^settings_ is reachable. It also asserts an expected-safe set is
present, so a server that registered nothing cannot pass vacuously. It needs no
credential and makes no network calls.
This exists because the deny-list is only correct as long as it names the right tools. Run it after every merge from upstream.
Attribution
Forked from MFYDev/ghost-mcp by Fanyang Meng. MIT licensed, same as upstream.
Available Tools
36 toolsmembers_addD
Inputs: email (required), name, note, labels, +1 more.
members_browseD
Inputs: page, limit, order, fields, +1 more.
members_editD
Inputs: id (required), name, note, email, +2 more.
members_readD
Inputs: id, email, fields.
newsletters_addD
Inputs: name (required), status, show_badge, description, +9 more.
newsletters_browseD
Inputs: page, limit, order, fields, +1 more.
newsletters_editD
Inputs: id (required), name, status, show_badge, +15 more.
newsletters_readD
Inputs: id, slug, fields.
offers_addD
Inputs: code (required), name (required), type (required), amount (required), +7 more.
offers_browseD
Inputs: page, limit, order, fields, +1 more.
offers_editD
Inputs: id (required), code, name, display_title, +1 more.
offers_readD
Inputs: id, code, fields.
pages_addD
Inputs: title (required), html, slug, tags, +21 more.
pages_browseD
Inputs: page, limit, order, fields, +2 more.
pages_draft_addD
Inputs: title (required), html, slug, tags, +20 more.
pages_draft_editD
Inputs: id (required), html, slug, tags, +21 more.
pages_editD
Inputs: id (required), updated_at (required), html, slug, +23 more.
pages_readD
Inputs: id, slug, fields, formats.
posts_addD
Inputs: title (required), html, slug, tags, +22 more.
posts_browseD
Inputs: page, limit, order, fields, +2 more.
posts_draft_addD
Inputs: title (required), html, slug, tags, +21 more.
posts_draft_editD
Inputs: id (required), html, slug, tags, +22 more.
posts_editD
Inputs: id (required), updated_at (required), html, slug, +24 more.
posts_readD
Inputs: id, slug, fields, formats.
roles_browseD
Inputs: page, limit, order, fields, +1 more.
roles_readD
Inputs: id, name, fields.
tags_addD
Inputs: name (required), slug, description.
tags_browseD
Inputs: page, limit, order, fields, +1 more.
tags_editD
Inputs: id (required), name, slug, description.
tags_readD
Inputs: id, slug, fields.
tiers_addD
Inputs: name (required), benefits, currency, visibility, +4 more.
tiers_browseD
Inputs: page, limit, order, fields, +2 more.
tiers_editD
Inputs: id (required), name, benefits, currency, +5 more.
tiers_readD
Inputs: id, slug, fields, include.
users_browseD
Inputs: page, limit, order, fields, +1 more.
users_readD
Inputs: id, slug, email, fields.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 36 tools
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.
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.
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.
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
Related MCP Connectors
Ghost MCP server for ChatGPT, Claude and any AI agent: list posts, create draft post, schedule post, send newsletter, list members and label members in your own Ghost account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Ghost yourself; Cotlet does not store your password and you need no Ghost API key. About the official Ghost API: Ghost has a full REST Admin API, but no official MCP server (checked 17 Oct 2026). The Admin API covers posts, pages, members, labels, newsletters, tiers and offers, and Ghost says everything Ghost Admin can do is also possible with the API. Setup and FAQ: https://cotlet.dev/integrations/ghost-api-mcp-server
Build and publish Ghost themes with your AI agent: pages, styles, patterns and previews.
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
A blog CMS that AI agents write into over MCP: Markdown drafts, versions, media, human approval.
Related MCP Servers
- 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.-
- 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 to manage Ghost CMS instance using LLM interfaces. Supports comprehensive CRUD operations on posts, members, newsletters, offers, tags, tiers, users, and webhooks.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely manage Ghost CMS blogs, including posts, pages, members, newsletters, tiers, and more via natural language.MIT