by mtane0412
Automate your Ghost blogs with the Ghost Admin API. Manage content and custom publishing workflows easily for Ghost CMS.
Connects to Ghost CMS Admin API for automated content management. Create, edit, and manage blog posts, pages, tags, authors, and members programmatically.
Ghost Admin API is a community-built MCP server published by mtane0412 that provides AI assistants with tools and capabilities via the Model Context Protocol. Automate your Ghost blogs with the Ghost Admin API. Manage content and custom publishing workflows easily for Ghost CMS. It is categorized under developer tools, productivity.
You can install Ghost Admin API in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Ghost Admin API is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Ghost Admin API for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Ghost Admin API is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Strong directory entry: Ghost Admin API surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We evaluated Ghost Admin API against two servers with overlapping tools; this profile had the clearer scope statement.
Ghost Admin API has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: Ghost Admin API is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, Ghost Admin API benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Ghost Admin API is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We wired Ghost Admin API into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
According to our notes, Ghost Admin API benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 41
A Model Context Protocol (MCP) server that integrates with the Ghost Admin API. This server enables programmatic access to Ghost CMS features including post management, page management, member management, and more.
Install the package using npm:
npm install @mtane0412/ghost-mcp-server
Create a new custom integration in your Ghost Admin dashboard under Settings > Integrations.
Set the following environment variables:
# macOS/Linux
export GHOST_URL="https://your-ghost-blog.com"
export GHOST_ADMIN_API_KEY="your_admin_api_key"
# Windows (PowerShell)
$env:GHOST_URL="https://your-ghost-blog.com"
$env:GHOST_ADMIN_API_KEY="your_admin_api_key"
Alternatively, you can create a .env file:
GHOST_URL=https://your-ghost-blog.com
GHOST_ADMIN_API_KEY=your_admin_api_key
After installation, start the server with:
npx @mtane0412/ghost-mcp-server
Retrieves a list of blog posts.
Input:
{
"limit": "number", // Optional: Number of posts to retrieve (1-100, default: 10)
"page": "number" // Optional: Page number (default: 1)
}
Retrieves a specific post by ID.
Input:
{
"id": "string" // Required: Post ID
}
Searches for posts.
Input:
{
"query": "string", // Required: Search query
"limit": "number" // Optional: Number of posts to retrieve (1-100, default: 10)
}
Creates a new post.
Input:
{
"title": "string", // Required: Post title
"html": "string", // Optional: HTML content
"lexical": "string", // Optional: Lexical content
"status": "string", // Optional: Post status (published/draft/scheduled)
"visibility": "string" // Optional: Visibility level (public/members/paid/tiers)
}
Updates an existing post.
Input:
{
"id": "string", // Required: Post ID
"title": "string", // Optional: Post title
"html": "string", // Optional: HTML content
"lexical": "string", // Optional: Lexical content
"status": "string" // Optional: Post status
}
Deletes a post.
Input:
{
"id": "string" // Required: Post ID
}
Retrieves a list of pages.
Input:
{
"limit": "number", // Optional: Number of pages to retrieve (1-100, default: 10)
"page": "number", // Optional: Page number (default: 1)
"order": "string", // Optional: Sort order
"formats": ["string"], // Optional: Content formats (html/mobiledoc/lexical)
"include": ["string"] // Optional: Related data to include (authors/tags)
}
Retrieves a list of members.
Input:
{
"limit": "number", // Optional: Number of members to retrieve (1-100, default: 10)
"page": "number", // Optional: Page number (default: 1)
"order": "string", // Optional: Sort order
"include": ["string"] // Optional: Related data to include (labels/newsletters)
}
Searches for members.
Input:
{
"query": "string", // Required: Search query
"limit": "number", // Optional: Number of members to retrieve (1-100, default: 10)
"include": ["string"] // Optional: Related data to include (labels/newsletters)
}
Uploads an image.
Input:
{
"file": "string", // Required: Base64 encoded image data
"purpose": "string" // Optional: Image purpose (image/profile_image/icon)
}
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspect
The Inspector will provide a URL to access debugging tools in your browser.
MIT License
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.