Browse PostsLABSCO SUMMARY
The whole Ghost admin surface, including the parts that are not content.
Post editing is the obvious use; the membership side is the one that saves real time - tiers, offers, newsletters and member records are all reachable in the same session, which is normally several screens of the Ghost admin. Errors come back as descriptive messages rather than raw API failures, which matters when the model has to decide what to do next.
What it is
A server over Ghost's Admin API, authenticated with JWT through the official admin client. Each Ghost entity gets the same shape of operations - browse, read, create, edit, delete - so the coverage is wide and predictable.
What you get
- Posts: list with filters, pagination and ordering, read by ID or slug, create with title, content and status, edit and delete
- Members: list, read by ID or email, create, update and remove
- Newsletters, offers and tiers: full browse, read, create, edit and delete on each
- Tags for organising content, invites for bringing staff in, and roles for reading permissions
- Users: list, read, update and remove
- Webhooks: list, add and delete, for wiring Ghost events to other systems
- Search with both fuzzy and exact matching, and readable output rather than raw API payloads
Requirements
Node, run with npx @fanyangmeng/ghost-mcp. Three environment variables: GHOST_API_URL pointing at your blog, GHOST_ADMIN_API_KEY, and GHOST_API_VERSION. The admin key carries whatever permissions Ghost grants it, so this reaches member records and staff accounts, not just published posts.
Setup effort
One command plus a key — npx -y @fanyangmeng/ghost-mcp, then supply credentials
USE CASES
01
Publishing a post you drafted in conversation
Create it with a title, body and status, then edit it in place rather than re-creating it after review.
02
Answering a question about a subscriber
Look the member up by email, read their record, and check which tier and offer they came in on.
03
Auditing what a site actually publishes
Browse posts with filters and ordering, then read the tags to see whether the taxonomy still matches the content.
04
Connecting Ghost to something else
List the existing webhooks, add the one you need, and delete the ones pointing at services you no longer run.
42 tools
Listed in project docs. Your client may show a different list.
Read PostAdd PostEdit PostDelete PostBrowse MembersRead MemberAdd MemberEdit MemberDelete MemberBrowse NewslettersRead NewsletterAdd NewsletterEdit NewsletterDelete NewsletterBrowse OffersRead OfferAdd OfferEdit OfferDelete OfferBrowse InvitesAdd InviteDelete InviteBrowse RolesRead RoleBrowse TagsRead TagAdd TagEdit TagDelete TagBrowse TiersRead TierAdd TierEdit TierDelete TierBrowse UsersRead UserEdit UserDelete UserBrowse WebhooksAdd WebhookDelete WebhookBEFORE YOU INSTALL
What to know first
Tools you get
42 tools named in the project's documentation.
Requires
- npx on PATH
- GHOST_ADMIN_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @fanyangmeng/ghost-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"ghost-mcp": {
"command": "npx",
"args": [
"-y",
"@fanyangmeng/ghost-mcp"
],
"env": {
"GHOST_API_URL": "<YOUR_GHOST_API_URL>",
"GHOST_ADMIN_API_KEY": "<YOUR_GHOST_ADMIN_API_KEY>",
"GHOST_API_VERSION": "v5.0"
}
}
}
}
