Ghost MCP Server
Ghost CMS management through 34 specialized tools for posts, pages, and members.
Data last scanned today · Reviewed today
Overview
Ghost MCP Server enables AI clients to interface with Ghost CMS instances using the Model Context Protocol. By connecting via the Ghost Admin API, the server exposes resources and tools for granular content and audience management. The server supports managing tags, posts, pages, members, newsletters, and membership tiers. It provides 34 distinct tools that allow users to create, retrieve, and update CMS entities directly from an AI-enabled environment.
Our verdict
This server carries a high-risk score of 32/100, primarily due to the lack of a read-only mode, meaning every installation provides full write access to your Ghost CMS instance. Given it is a community-maintained project without an official editorial review or integrated OAuth support, it should be restricted to private, experimental environments by users who have verified the source code themselves.
- Provides 34 specific tools for granular Ghost CMS management
- Maintains a high 90 percent test coverage
- Uses a small footprint with only 17 direct dependencies
- Includes well-documented resource schemas for CMS entities
- Lacks a read-only configuration, enabling default full write access
- Community-maintained with no official vendor affiliation
- Missing OAuth support for secure credential management
Setup
{
"mcpServers": {
"ghost-mcp-server": {
"args": [
"-y",
"@jgardner04/ghost-mcp-server"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| ghost_create_tag | Creates a new tag. | medium |
| ghost_get_tags | Retrieves a list of tags with optional filtering. | low |
| ghost_get_tag | Retrieves a single tag by ID or slug. | low |
| ghost_update_tag | Updates an existing tag. | medium |
| ghost_delete_tag | Deletes a tag permanently. | high |
| ghost_upload_image | Downloads, processes, and uploads an image to Ghost. | medium |
| ghost_create_post | Creates a new post. | medium |
| ghost_get_posts | Retrieves posts with pagination and filtering. | low |
| ghost_get_post | Retrieves a single post by ID or slug. | low |
| ghost_search_posts | Searches posts by title/content. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the system requirements for running the Ghost MCP Server?
You must have Node.js version 18.0.0 or higher installed on your system.
›What information do I need to configure the server?
You must provide a valid Ghost Admin API URL and a corresponding Admin API key to connect to your Ghost instance.
›How do I upload images for my posts or pages?
You should use the ghost_upload_image tool to download and upload an image to Ghost first, which will provide you with the required Ghost-hosted URL for your content.
›Are there functional differences between posts and pages in this server?
Yes, while both support similar management tools, pages do not support tag functionality, whereas posts do.
›On which port does the server typically listen?
The server is configured to listen on port 3001 by default when initialized.
Badge
Maintain this server? Add the live badge to your README.