Ghost Cms MCP Server

A comprehensive Model Context Protocol (MCP) server for Ghost CMS with full CRUD operations, bulk actions, and advanced features. Developed by

Local serverstdioTypeScript

What is the Ghost Cms MCP server?

Ghost Cms MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A comprehensive Model Context Protocol (MCP) server for Ghost CMS with full CRUD operations, bulk actions, and advanced features. Developed by Sivasubramanian Ramanathan, Product Owner & Innovation Catalyst previously at BIS Innovation.

What you get

A comprehensive Model Context Protocol (MCP) server for Ghost CMS that provides full automation capabilities for Ghost blogs through AI assistants like Claude Desktop, Cursor, and other MCP-compatible clients.

Setting it up

The server ships on npm as ghost-cms-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 and credentials

You will need 3 environment variables: GHOST_URL, GHOST_ADMIN_API_KEY, GHOST_CONTENT_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.

Before you rely on it

  • 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.
  • 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 cms mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by siva-sub; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

How to install the Ghost Cms MCP server

{
  "mcpServers": {
    "ghost-cms": {
      "command": "npx",
      "args": ["-y", "ghost-cms-mcp-server"],
      "env": {
        "GHOST_URL": "your-value",
        "GHOST_ADMIN_API_KEY": "your-value",
        "GHOST_CONTENT_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
GHOST_URLEndpoint or connection string the server talks to.Yes
GHOST_ADMIN_API_KEYCredential the server authenticates with.Yes
GHOST_CONTENT_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

It connects Ghost Cms to MCP-compatible AI assistants such as Claude and Cursor. Instead of copying data back and forth by hand, the assistant works with Ghost Cms directly.