Ghost Blog MCP Server
Connects AI agents to a Ghost blog through the Ghost Admin and Content APIs. Provides context-safe read tools for listing posts, pages, tags, and authors (titles/metadata only) plus on-demand fetching of a single post's full body (Lexical parsed to plain text or raw HTML), and, with an admin key, write tools to create, update, publish/schedule, and delete posts, pages, and tags. Supports a read-only mode using only a Content API key.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Features
Context-safe listing — compact one-line tables (date, status, title, tags, author) for posts, pages, tags, and authors. No bodies in list output, so agents can triage the whole site without context overflow.
On-demand detail fetching — metadata plus a truncated body preview via
get_post(), or the full body viaget_post_content()(the Lexical document parsed to readable text, or raw HTML).Full mode with an admin key — create, update, publish/schedule, and delete posts, pages, and tags through the Ghost Admin API.
Read-only mode with a content key — every read tool works with just a Content API key; write tools then report that
GHOST_ADMIN_KEYis required. No admin key needed to let an agent read your blog.Stdlib-only admin auth — the Admin API's HS256 JWT is built with
hmac/base64/json; no extrajwtdependency.Draft → confirm pattern — every write tool's docstring asks the agent to confirm with the user first; posts and pages are live the moment they publish.
Connection check — verify credentials and connectivity, and report which auth mode (admin / content-only / unconfigured) the server is running in.
Three transports — stdio (default), Streamable HTTP, and SSE, selected with
MCP_TRANSPORT; a Docker image is published to GHCR on every push tomain.
Related MCP server: Ghost MCP Server
Tools
Read Tools
Tool | Description |
| Verify credentials and connectivity, with the current auth mode (admin / content-only / unconfigured) and the site title. Run first when debugging a new setup. |
| Compact one-line-per-post table: title, status, tags, author, date. Filters: status, tag, author; plus paging and ordering. Drafts are visible in admin mode only. |
| Metadata + a truncated body preview (default 1500 chars, adjustable) for one post by id or slug. |
| The FULL body of one post, on demand — |
| Compact table of static pages: title, status, tags, date. |
| Metadata + a truncated body preview for one static page by id or slug. |
| All tags with post/page counts where the API provides them (counts are admin-mode only). |
| The site's authors — admin |
Write Tools (admin key required)
Tool | Description |
| Create a post: title + body as HTML (sent with |
| Update a post. |
| Publish, unpublish, or schedule a post ( |
| Permanently delete a post. |
| Create a static page (same shape as |
| Update a static page (same shape as |
| Permanently delete a page. |
| Create a tag (name required; slug/description optional). |
| Update a tag's name, slug, and/or description. |
| Permanently delete a tag. |
All write tools require GHOST_ADMIN_KEY — in read-only mode they return a clear configuration error naming it.
Each tool's docstring asks the agent to confirm with the user first; published posts and pages are live immediately.
Deployment
Option 1 — Container (Recommended)
Running as a container means every client always uses the latest version.
The image is built automatically on every push to main via GitHub Actions
and published to GitHub Container Registry.
docker-compose / Portainer
services:
ghost-blog-mcp:
image: ghcr.io/glitch3dpenguin/ghost-blog-mcp:latest
container_name: ghost-blog-mcp
restart: unless-stopped
ports:
- "8000:8000"
environment:
GHOST_URL: "https://your-ghost-site.example"
GHOST_ADMIN_KEY: "<key id>:<64-char-hex-secret>"
GHOST_CONTENT_KEY: "optional_content_key"
MCP_TRANSPORT: "streamable-http"
PORT: "8000"docker compose up -dThe MCP endpoint will be available at the root path (the server is configured to serve at /, not FastMCP's default /mcp):
http://<host>:8000/With MCP_TRANSPORT=sse the endpoint is http://<host>:8000/sse.
Portainer via Stack
In Portainer, go to Stacks → Add stack
Paste the
docker-compose.ymlcontents aboveFill in your Ghost credentials in the environment section
Deploy
Connecting your AI client to the container
Field | Value |
Transport | Streamable HTTP |
URL |
|
In claude_desktop_config.json:
{
"mcpServers": {
"ghost-blog": {
"type": "http",
"url": "http://<your-server-ip>:8000/"
}
}
}Tip: If you're running behind a reverse proxy (Nginx, Caddy, Traefik), you can expose this on a subdomain with TLS instead of a raw port.
Option 2 — Local (stdio)
Run the server as a local process on the same machine as your AI client. No container required, but each machine needs its own install.
Install
git clone https://github.com/Glitch3dPenguin/ghost-blog-mcp.git
cd ghost-blog-mcp
pip install -r requirements.txtAI client configuration
In claude_desktop_config.json (or equivalent):
{
"mcpServers": {
"ghost-blog": {
"command": "python3",
"args": ["/absolute/path/to/ghost_blog_mcp.py"],
"env": {
"GHOST_URL": "https://your-ghost-site.example",
"GHOST_ADMIN_KEY": "<key id>:<64-char-hex-secret>",
"GHOST_CONTENT_KEY": "optional_content_key"
}
}
}
}⚠️ The path in
argsmust be absolute. AI clients cannot resolve relative paths.
Windows:
["C:\\Users\\Name\\ghost-blog-mcp\\ghost_blog_mcp.py"]Mac/Linux:
["/home/username/ghost-blog-mcp/ghost_blog_mcp.py"]
Environment Variables
Variable | Required | Description |
| ✅ | Your Ghost site URL, e.g. |
| ✅ for writes | Admin API key, format |
| — | Content API key, from Ghost admin → Integrations → Content API. With no admin key set, the server runs in read-only mode. Never logged. |
| — |
|
| — | Port to bind on for HTTP transports (default: |
Auth modes: admin key set → full mode (reads and writes via the Admin API) · only a content key →
read-only mode (reads via the Content API) · neither → check_connection reports a configuration problem
naming the missing variables.
See Ghost's API documentation for credential setup — Admin and Content API keys are created under Integrations in the Ghost admin panel.
Other Ghost MCP options
This is a community project. Ghost does not ship an official MCP server; every Ghost MCP integration is third-party, and this is not the only one:
Option | Type | What it is |
This server | Self-hosted | Context-safe MCP server for the Ghost Admin + Content APIs — stdio, Streamable HTTP, and SSE, with a Docker image on GHCR. |
Self-hosted | Popular TypeScript server for the Ghost Admin API — post management with an OAuth-style key flow. | |
Self-hosted | TypeScript server for managing a Ghost instance from LLM interfaces. | |
Self-hosted | Node/TypeScript server with full CRUD, bulk actions, and a test suite. | |
Self-hosted | Ghost Admin API server covering posts, pages, members, and more. | |
Self-hosted | Python (FastMCP) server with read-only Content API and read/write Admin API access. |
If you just need a quick Admin-API integration, one of the above may save you the ops work. This server is for teams that want a context-safe read model, an optional read-only mode with a content key, and their own credentials on their own infrastructure.
Branding & trademarks
Ghost is a trademark of its respective owners. This project is not affiliated with, endorsed by, or sponsored by Ghost. It is a community server that talks to Ghost's public Admin and Content APIs using your own credentials.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Build and publish Ghost themes with your AI agent: pages, styles, patterns and previews.
Ghost MCP server for ChatGPT, Claude and any AI agent: list posts, create draft post, schedule post, send newsletter, list members and label members in your own Ghost account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Ghost yourself; Cotlet does not store your password and you need no Ghost API key. About the official Ghost API: Ghost has a full REST Admin API, but no official MCP server (checked 17 Oct 2026). The Admin API covers posts, pages, members, labels, newsletters, tiers and offers, and Ghost says everything Ghost Admin can do is also possible with the API. Setup and FAQ: https://cotlet.dev/integrations/ghost-api-mcp-server
Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
Publish and run a blog on your own domain from any AI agent, with hosting and technical SEO.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Ghost CMS instances through the Admin API, supporting content operations (posts, tags), member management, newsletters, tiers, offers, and webhooks through natural language interactions.8 npm1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with Ghost CMS through the Ghost Admin API via LLM interfaces. It provides comprehensive tools for managing posts, members, newsletters, and other site entities through secure JWT authentication.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Ghost CMS content including posts, members, users, tags, tiers, offers, newsletters, invites, roles, and webhooks via the Ghost Admin API.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Ghost CMS sites through both Content (read-only) and Admin (read/write) APIs, allowing natural language management of posts, pages, tags, and settings.1MIT