Skip to main content
Glama
Ghost Blog MCP Server

Ghost Blog MCP Server


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 via get_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_KEY is 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 extra jwt dependency.

  • 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 to main.


Related MCP server: Ghost MCP Server

Tools

Read Tools

Tool

Description

check_connection

Verify credentials and connectivity, with the current auth mode (admin / content-only / unconfigured) and the site title. Run first when debugging a new setup.

list_posts

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.

get_post

Metadata + a truncated body preview (default 1500 chars, adjustable) for one post by id or slug.

get_post_content

The FULL body of one post, on demand — lexical (the Lexical document parsed to readable plain text, default) or html (raw).

list_pages

Compact table of static pages: title, status, tags, date.

get_page

Metadata + a truncated body preview for one static page by id or slug.

list_tags

All tags with post/page counts where the API provides them (counts are admin-mode only).

list_authors

The site's authors — admin /users/ in full mode, content /authors/ in read-only mode.

Write Tools (admin key required)

Tool

Description

create_post

Create a post: title + body as HTML (sent with ?source=html) or a Lexical JSON string, status (default draft), auto-creating tag names, authors by email/id, optional publish_at for scheduling.

update_post

Update a post. updated_at is required (fetch latest first); tags/authors are REPLACED, not merged; save_revision supported.

set_post_status

Publish, unpublish, or schedule a post (draft / published, optional publish_at).

delete_post

Permanently delete a post.

create_page

Create a static page (same shape as create_post, no scheduling).

update_page

Update a static page (same shape as update_post).

delete_page

Permanently delete a page.

create_tag

Create a tag (name required; slug/description optional).

update_tag

Update a tag's name, slug, and/or description.

delete_tag

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

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 -d

The 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

  1. In Portainer, go to Stacks → Add stack

  2. Paste the docker-compose.yml contents above

  3. Fill in your Ghost credentials in the environment section

  4. Deploy

Connecting your AI client to the container

Field

Value

Transport

Streamable HTTP

URL

http://<your-server-ip>:8000/

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.txt

AI 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 args must 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

GHOST_URL

✅

Your Ghost site URL, e.g. https://your-ghost-site.example (a trailing / is fine — it is stripped in code).

GHOST_ADMIN_KEY

✅ for writes

Admin API key, format <key id>:<64-char-hex-secret>, from Ghost admin → Integrations → Admin API. Enables full read/write mode. Never logged.

GHOST_CONTENT_KEY

—

Content API key, from Ghost admin → Integrations → Content API. With no admin key set, the server runs in read-only mode. Never logged.

MCP_TRANSPORT

—

streamable-http, sse, or stdio (default: stdio)

PORT

—

Port to bind on for HTTP transports (default: 8000)

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.

MFYDev/ghost-mcp

Self-hosted

Popular TypeScript server for the Ghost Admin API — post management with an OAuth-style key flow.

hithereiamaliff/mcp-ghostcms

Self-hosted

TypeScript server for managing a Ghost instance from LLM interfaces.

siva-sub/ghost-cms-mcp-server

Self-hosted

Node/TypeScript server with full CRUD, bulk actions, and a test suite.

mtane0412/ghost-mcp-server

Self-hosted

Ghost Admin API server covering posts, pages, members, and more.

thenets/ghost-mcp

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…

    Related MCP Connectors

    Related MCP Servers