Provides tools for managing Ghost CMS content, including posts, members, newsletters, offers, invites, roles, tags, tiers, users, and webhooks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ghost-mcp-azure What are the latest published posts on my Ghost blog?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server for interacting with Ghost CMS through LLM interfaces like Claude. This server provides secure and comprehensive access to your Ghost blog, leveraging JWT authentication and a rich set of MCP tools for managing posts, users, members, tiers, offers, and newsletters.
Secure Ghost Admin API requests with @tryghost/admin-api
Comprehensive entity access including posts, users, members, tiers, offers, and newsletters
Advanced search functionality with both fuzzy and exact matching options
Detailed, human-readable output for Ghost entities
Robust error handling using custom GhostError exceptions
Integrated logging support via MCP context for enhanced troubleshooting
Related MCP server: ghost-mcp-secure
To use this with MCP clients, for instance, Claude Desktop, add the following to your claude_desktop_config.json:
{
"mcpServers": {
"ghost-mcp": {
"command": "npx",
"args": ["-y", "@fanyangmeng/ghost-mcp"],
"env": {
"GHOST_API_URL": "https://yourblog.com",
"GHOST_ADMIN_API_KEY": "your_admin_api_key",
"GHOST_API_VERSION": "v5.0"
}
}
}
}The following Ghost CMS resources are available through this MCP server:
Posts: Articles and content published on your Ghost site.
Members: Registered users and subscribers of your site.
Newsletters: Email newsletters managed and sent via Ghost.
Offers: Promotional offers and discounts for members.
Invites: Invitations for new users or staff to join your Ghost site.
Roles: User roles and permissions within the Ghost admin.
Tags: Organizational tags for posts and content.
Tiers: Subscription tiers and plans for members.
Users: Admin users and staff accounts.
Webhooks: Automated event notifications to external services.
This MCP server exposes a comprehensive set of tools for managing your Ghost CMS via the Model Context Protocol. Each resource provides a set of operations, typically including browsing, reading, creating, editing, and deleting entities. Below is a summary of the available tools:
Browse Posts: List posts with optional filters, pagination, and ordering.
Read Post: Retrieve a post by ID or slug.
Add Post: Create a new post with title, content, and status.
Edit Post: Update an existing post by ID.
Delete Post: Remove a post by ID.
Browse Members: List members with filters and pagination.
Read Member: Retrieve a member by ID or email.
Add Member: Create a new member.
Edit Member: Update member details.
Delete Member: Remove a member.
Browse Newsletters: List newsletters.
Read Newsletter: Retrieve a newsletter by ID.
Add Newsletter: Create a new newsletter.
Edit Newsletter: Update newsletter details.
Delete Newsletter: Remove a newsletter.
Browse Offers: List offers.
Read Offer: Retrieve an offer by ID.
Add Offer: Create a new offer.
Edit Offer: Update offer details.
Delete Offer: Remove an offer.
Browse Invites: List invites.
Add Invite: Create a new invite.
Delete Invite: Remove an invite.
Browse Roles: List roles.
Read Role: Retrieve a role by ID.
Browse Tags: List tags.
Read Tag: Retrieve a tag by ID or slug.
Add Tag: Create a new tag.
Edit Tag: Update tag details.
Delete Tag: Remove a tag.
Browse Tiers: List tiers.
Read Tier: Retrieve a tier by ID.
Add Tier: Create a new tier.
Edit Tier: Update tier details.
Delete Tier: Remove a tier.
Browse Users: List users.
Read User: Retrieve a user by ID or slug.
Edit User: Update user details.
Delete User: Remove a user.
Browse Webhooks: List webhooks.
Add Webhook: Create a new webhook.
Delete Webhook: Remove a webhook.
Each tool is accessible via the MCP protocol and can be invoked from compatible clients. For detailed parameter schemas and usage, see the source code in
src/tools/.
Ghost MCP Server employs a custom GhostError exception to handle API communication errors and processing issues. This ensures clear and descriptive error messages to assist with troubleshooting.
This fork can also run as a remote MCP server (Streamable HTTP transport) hosted on Azure Functions (Flex Consumption plan), following the official Microsoft pattern. The Functions host runs the server as an MCP custom handler: host.json launches node build/index.js, an Express app exposing the MCP endpoint at /mcp in stateless mode (a fresh server + transport per request).
src/mcpServer.ts — createServer() factory registering all Ghost resources, tools and prompts (shared by both entry points).
src/server.ts — stdio entry point (local use with Claude Desktop, unchanged).
src/index.ts — HTTP entry point (Express + StreamableHTTPServerTransport, stateless) used by Azure Functions.
host.json — mcp-custom-handler configuration profile, anonymous auth at the host level (OAuth is enforced by Easy Auth, see below).
infra/ — Bicep modules (azd) provisioning: Flex Consumption Function App (Node 22), storage with private endpoints + VNet, App Insights/Log Analytics, user-assigned managed identity, and an Entra ID app registration + Easy Auth so only authenticated Microsoft Entra users can call the MCP endpoint.
Ghost credentials are read from environment variables / app settings — never hardcoded:
Setting | Description |
| Base URL of your Ghost site, e.g. |
| Admin API key (Ghost Admin → Settings → Integrations → Add custom integration) |
| API version, defaults to |
For local development, fill these values in local.settings.json (dummy placeholders are committed; do not commit real keys).
npm install
npm run build
func start # Azure Functions Core Tools v4.5+The MCP endpoint is then available at http://localhost:7071/mcp. .vscode/mcp.json contains local-mcp-server and remote-mcp-server configurations to test it from GitHub Copilot in VS Code.
Deployment uses the Azure Developer CLI (azd) with the Bicep files under infra/:
azd auth login
azd env new ghost-mcp-prod
azd env set GHOST_API_URL https://yourblog.ghost.io
azd env set GHOST_ADMIN_API_KEY <your_admin_api_key>
azd env set PRE_AUTHORIZED_CLIENT_IDS aebc6443-996d-45c2-90f0-388ff96faa56 # pre-authorize VS Code
azd upazd up provisions the Flex Consumption function app, deploys the code (remote build), configures the Ghost app settings, and sets up Entra ID authentication. When it completes, note the function app name, then start the remote-mcp-server configuration in .vscode/mcp.json and enter <your-function-app>.azurewebsites.net when prompted.
To remove all resources: azd down.
Fork repository
Create feature branch
Commit changes
Create pull request
MIT
Inputs: email (required), role_id (required).
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: email (required), name, note, labels, +1 more.
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: id (required), name, note, email, +2 more.
Inputs: id, email.
Inputs: name (required), status, show_badge, description, +9 more.
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: id (required), name, status, show_badge, +15 more.
Inputs: id, slug.
Inputs: code (required), name (required), type (required), amount (required), +7 more.
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: id (required), code, name, display_title, +1 more.
Inputs: id, code.
Inputs: title (required), html, slug, tags, +22 more.
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: id (required), updated_at (required), html, slug, +24 more.
Inputs: id, slug.
Inputs: page, limit, order, filter.
Inputs: id, name.
Inputs: name (required), slug, description.
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: id (required), name, slug, description.
Inputs: id, slug.
Inputs: name (required), benefits, currency, visibility, +4 more.
Inputs: page, limit, order, filter, +1 more.
Inputs: id (required).
Inputs: id (required), name, benefits, currency, +5 more.
Inputs: id, slug, include.
Inputs: page, limit, order, filter.
Inputs: id (required).
Inputs: id (required), bio, name, slug, +5 more.
Inputs: id, slug, email.
Inputs: event (required), target_url (required), name, secret, +2 more.
Inputs: id (required).
Inputs: id (required), name, event, target_url, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 42 tools
Tools follow a resource_action pattern that clearly separates resources (posts, members, tags) and CRUD-like operations (browse, read, add, edit, delete). Boundaries are mostly clear, though browse vs read distinction is slightly ambiguous without descriptions.
Every tool consistently uses resource_action format with plural resources and a small fixed verb set (browse, read, add, edit, delete). No mixing of conventions.
42 tools is heavy for a Ghost CMS surface, and many are mechanical per-resource variants. This bloats the toolset beyond what an agent can easily navigate.
Coverage is good across many resources, but many resources lack edit/delete (newsletters has no browse? invites lacks read/edit; users lacks add; webhooks lack browse/read). No descriptions make gaps harder to assess, but lifecycle coverage is uneven.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
Hosted MCP server for AI agents to post to LinkedIn profiles and X and upload to YouTube.