Ghost
An MCP Server for managing posts on Ghost CMS
claude mcp add --transport stdio jgardner04-ghost-mcp-server node src/server.js \ --env GHOST_ADMIN_API_KEY="your_admin_api_key" \ --env GHOST_ADMIN_API_URL="https://your-ghost-url/ghost"
How to use
This Ghost MCP Server exposes Ghost CMS management operations as MCP tools. It implements 34 tools across seven resource types (tag, post, page, member, newsletter, tier, and image handling) that allow an MCP client to create, read, update, delete, and search Ghost content and configurations. Once the server is running (default at http://localhost:3001/), an MCP client can discover available resources and tools via the root endpoint and begin issuing tool invocations such as ghost_create_post, ghost_update_tag, ghost_get_pages, ghost_search_members, or ghost_upload_image to manage a Ghost blog programmatically. The tools mirror the Ghost Admin API surface and support common operations like creating posts with HTML content and metadata, uploading images for use in content, managing tags and pages, handling members and newsletters, and configuring memberships and plans.
How to install
Prerequisites:
- Node.js 18.x or higher installed on your system
- Access to a Ghost Admin API URL and a valid Admin API key
- Git to clone the repository (optional but recommended)
-
Clone the repository git clone https://github.com/jgardner04/Ghost-MCP-Server.git cd Ghost-MCP-Server
-
Install dependencies npm install
-
Configure environment variables Create a .env file or export variables in your environment with the following values:
- GHOST_ADMIN_API_URL: Your Ghost Admin API URL (e.g., https://your-ghost-site.com/ghost/api/admin)
- GHOST_ADMIN_API_KEY: Your Ghost Admin API key
-
Run the MCP server npm run start
or if you run directly via node
node src/server.js
-
Verify the server is running Open http://localhost:3001/ in your browser or call the MCP discovery endpoint to confirm the server exposes its capabilities.
Additional notes
Tips and common considerations:
- Ensure the Ghost Admin API URL is reachable from the MCP server host and that the Admin API key has sufficient permissions for the desired operations.
- The MCP server typically exposes a root discovery endpoint (e.g., http://localhost:3001/) where clients can retrieve the capabilities and available tools.
- If you change the Ghost API URL or credentials, restart the MCP server to apply the new configuration.
- For image handling (ghost_upload_image), the service expects a publicly accessible image URL. The tool will upload and return the Ghost image URL for use in content.
- When creating posts or pages with complex content, use the html field to include your content structure and media embeds. SEO fields like meta_title and meta_description are optional but recommended for better search visibility.
- Review rate limits or permission constraints of your Ghost installation, as some operations may be restricted by role or API usage limits.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.