ghost

A Model Context Protocol (MCP) server for interacting with Ghost CMS through LLM interfaces like Claude. Allow you to control your Ghost blog by simply asking Claude etc.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio mfydev-ghost-mcp npx -y @fanyangmeng/ghost-mcp \
  --env GHOST_API_URL="https://yourblog.com" \
  --env GHOST_API_VERSION="v5.0" \
  --env GHOST_ADMIN_API_KEY="your_admin_api_key"

How to use

Ghost MCP Server provides a bridge to manage your Ghost CMS via MCP clients (e.g., Claude Desktop) using the Ghost Admin API. It exposes resources such as posts, members, newsletters, offers, invites, roles, tags, tiers, users, and webhooks, with common operations like browse, read, add, edit, and delete. The server uses the official @tryghost/admin-api client for authenticated interactions and returns structured, human-readable results suitable for LLM-based tooling. To get started, configure your MCP client with the Ghost server entry, including the Ghost API URL, admin API key, and API version, then invoke the available tools to manage content and settings programmatically.

How to install

Prerequisites:

Node.js and npm installed on your machine
Access to the Ghost Admin API (URL and Admin API Key)

Install and run:

Install the MCP server package from npm (as demonstrated by the usage example): npx -y @fanyangmeng/ghost-mcp
Alternatively, install the package globally or in a project if your deployment workflow requires it: npm install @fanyangmeng/ghost-mcp
Configure environment variables for authentication and API access. Example (adjust to your Ghost instance): export GHOST_API_URL="https://yourblog.com" export GHOST_ADMIN_API_KEY="your_admin_api_key" export GHOST_API_VERSION="v5.0"
Run the MCP server through your preferred runner (the README demonstrates using npx in an MCP config). If using Docker or another container approach, adapt accordingly based on your deployment method.

Additional notes

Tips and caveats:

Ensure the GHOST_API_URL and GHOST_ADMIN_API_KEY have the correct permissions to access the Ghost Admin API.
API version (GHOST_API_VERSION) should match your Ghost installation (default v5.0 in examples).
When using MCP clients, you can embed the server reference in your claude_desktop_config.json or equivalent, enabling rich tool support for posts, members, newsletters, and more.
If you upgrade Ghost or the Ghost MCP package, review breaking changes in v0.1.0 migration notes to adjust environment variables or usage patterns.
Check network access from your MCP runner to the Ghost Admin API, including any required TLS/CA certificates in restricted environments.

Related MCP Servers

iterm

530

A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance

ZMCPTools

A custom TypeScript MCP Server intended to be used with Claude Code

mcp-gemini

This project provides a dedicated MCP (Model Context Protocol) server that wraps the @google/genai SDK. It exposes Google's Gemini model capabilities as standard MCP tools, allowing other LLMs (like Cline) or MCP-compatible systems to leverage Gemini's features as a backend workhorse.

mcp-file-operations

A Model Context Protocol (MCP) server that provides enhanced file operation capabilities with streaming, patching, and change tracking support.

mcp-web-search-tool

A MCP server providing real-time web search capabilities to any AI model.

mcp -webscan

A Model Context Protocol (MCP) server for web content scanning and analysis. This server provides tools for fetching, analyzing, and extracting information from web pages.