Ghost MCP Server

Ghost MCP Server for interacting with Ghost CMS API. The ghost mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

A Model Context Protocol (MCP) server that integrates with the Ghost Admin API. This server enables programmatic access to Ghost CMS features including post management, page management, member management, and more.

• Post Management (create, read, update, delete, search)
• Page Management (create, read, update, delete)
• Tag Management
• Author Management
• Member Management (create, read, update, delete, search)
• Image Upload Support

Its toolset

Everything the assistant can do here goes through one of these:

• get_posts — Input: json { "limit": "number", // Optional: Number of posts to retrieve (1-100, default: 10) "page": "number" // Optional: Page number (default: 1)
• get_post — The get_post tool exposed by this server
• search_posts — Input: json { "query": "string", // Required: Search query "limit": "number" // Optional: Number of posts to retrieve (1-100, default: 10) }
• create_post — Input: json { "title": "string", // Required: Post title "html": "string", // Optional: HTML content "lexical": "string", // Optional: Lexical
• update_post — Input: json { "id": "string", // Required: Post ID "title": "string", // Optional: Post title "html": "string", // Optional: HTML content "lexical"
• delete_post — The delete_post tool exposed by this server
• get_pages — Input: json { "limit": "number", // Optional: Number of pages to retrieve (1-100, default: 10) "page": "number", // Optional: Page number (default
• get_members — Input: json { "limit": "number", // Optional: Number of members to retrieve (1-100, default: 10) "page": "number", // Optional: Page number (default
• search_members — Input: json { "query": "string", // Required: Search query "limit": "number", // Optional: Number of members to retrieve (1-100, default: 10)
• upload_image — Input: json { "file": "string", // Required: Base64 encoded image data "purpose": "string" // Optional: Image purpose (image/profile_image/icon) }
• Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP

Adding it to your client

The server ships on npm as @mtane0412/ghost-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need 2 environment variables: GHOST_URL, GHOST_ADMIN_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js (v18 or higher recommended) - Ghost CMS instance - Ghost Admin API key

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ghost's toolset — get_posts, get_post, search_posts and 8 more — is a fair guide to whether it matches your workflow. It is maintained by mtane0412; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ghost's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ghost.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ghost mcp server does with a few real requests.