Manage Ghost CMS Content via LLM
An MCP server for managing a Ghost CMS blog - posts, members, newsletters, tiers, offers, and webhooks - from an LLM interface.
Maintainer of this project? Claim this page to edit the listing.
0.2.0Add to Favorites
Why it matters
Integrate your Ghost CMS with LLM interfaces for seamless content management. Securely access and manipulate posts, members, and newsletters using natural language commands.
Outcomes
What it gets done
List, read, create, edit, and delete Ghost posts.
Manage Ghost member data including creation and updates.
Handle newsletter content creation and management.
Securely authenticate and interact with the Ghost Admin API.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-ghost | bash Capabilities
Tools your agent gets
List posts with optional filters, pagination, and sorting
Get a post by ID or slug
Create a new post with title, content, and status
Update an existing post by ID
Delete a post by ID
List members with filters and pagination
Get a member by ID or email
Create a new member
Overview
Ghost MCP Server
This MCP server gives an LLM full CRUD access to a Ghost CMS blog: posts, members, newsletters, offers, tiers, tags, roles, invites, users, and webhooks, authenticated via the Ghost Admin API with JWT and returning human-readable output. Use it to manage Ghost blog content and membership from an LLM interface. Exercise care with edit and delete operations, which act directly and irreversibly on a live production blog.
What it does
Gives an LLM interface full administrative access to a Ghost CMS blog through MCP, covering posts, members, newsletters, offers, invites, roles, tags, tiers, users, and webhooks. It authenticates securely against the Ghost Admin API using @tryghost/admin-api and JWT, supports both fuzzy and exact search, returns detailed human-readable output for Ghost entities, and uses custom GhostError exceptions with MCP-context logging for clear troubleshooting when something goes wrong.
When to use - and when NOT to
Use it to manage a Ghost blog's content and membership programmatically from an LLM chat interface: publishing or editing posts, managing subscriber tiers and promotional offers, sending newsletters, administering users, roles, and invites, or wiring up webhooks to external services. It is Ghost-specific and won't work with other CMS platforms, and it requires a Ghost Admin API key with the right permissions. Because most operations - especially edit and delete - act directly and irreversibly on a live blog, exercise care before deleting posts, members, or other entities on production content.
Capabilities
Each Ghost resource exposes a different depth of CRUD operations. Posts support the full set - browse with filters/pagination/ordering, read by ID or slug, add with title/content/status, edit, and delete. Members, Newsletters, Offers, and Tags likewise support browse/read/add/edit/delete, with Members specifically readable by ID or email and Tags readable by ID or slug. Tiers also gets the full five operations. Invites are more limited - browse and add and delete, with no read or edit step in between. Roles is read-only in effect: browse and read, nothing else. Users support browse, read by ID or slug, edit, and delete, but this server does not add new user accounts. Webhooks support browse, add, and delete, without a dedicated read or edit tool.
How to install
{
"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"
}
}
}
}
Add this to claude_desktop_config.json (or an equivalent MCP client config), filling in the blog's URL, its Ghost Admin API key, and the Ghost API version being targeted. Detailed parameter schemas for each tool live in the project's src/tools/ source directory.
Who it's for
Ghost site owners and editors who want to manage posts, members, and newsletters directly from an LLM chat interface, and developers building content-ops or membership-management workflows on top of Ghost's Admin API without writing their own API client from scratch.
Source README
Ghost MCP Server
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.
Features
- 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
GhostErrorexceptions - Integrated logging support via MCP context for enhanced troubleshooting
Usage
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"
}
}
}
}
Available Resources
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.
Available Tools
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:
Posts
- 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.
Members
- 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.
Newsletters
- 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.
Offers
- 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.
Invites
- Browse Invites: List invites.
- Add Invite: Create a new invite.
- Delete Invite: Remove an invite.
Roles
- Browse Roles: List roles.
- Read Role: Retrieve a role by ID.
Tags
- 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.
Tiers
- 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.
Users
- Browse Users: List users.
- Read User: Retrieve a user by ID or slug.
- Edit User: Update user details.
- Delete User: Remove a user.
Webhooks
- 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/.
Error Handling
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.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.