Ghost CMS MCP Server

Ghost CMS MCP server enabling AI agents to interact with Ghost publishing platform — reading and creating posts and pages, managing members and subscriptions, querying tags and authors, publishing content, and integrating Ghost's headless CMS capabilities into agent-driven content creation, editorial, and newsletter automation workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Developer Tools ghost cms blogging content mcp-server publishing newsletter
⚙ Agent Friendliness
77
/ 100
Can an agent use this?
🔒 Security
76
/ 100
Is it safe for agents?
⚡ Reliability
71
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
72
Documentation
78
Error Messages
72
Auth Simplicity
85
Rate Limits
82

🔒 Security

TLS Enforcement
90
Auth Strength
75
Scope Granularity
70
Dep. Hygiene
72
Secret Handling
75

HTTPS recommended. Content API (public) vs Admin API (sensitive). Community MCP server. Protect Admin API key — it grants full read/write to Ghost. Self-hosted requires proper HTTPS setup.

⚡ Reliability

Uptime/SLA
70
Version Stability
72
Breaking Changes
72
Error Recovery
70
AF Security Reliability

Best When

An agent needs to create, manage, or query Ghost CMS content — for AI-assisted blogging, newsletter automation, or content management workflows.

Avoid When

You're using WordPress, Contentful, Sanity, or another CMS — or if you need Ghost theme customization rather than content management.

Use Cases

  • • Creating and publishing blog posts from content generation agents
  • • Querying post library and drafts from editorial workflow agents
  • • Managing newsletter subscribers and members from audience management agents
  • • Generating content calendars and scheduling from planning agents
  • • Extracting post analytics and engagement data from analytics agents
  • • Automating tag and author management from content operations agents

Not For

  • • Teams using WordPress, Contentful, or other CMS platforms (use their specific MCPs)
  • • Self-hosted Ghost with non-standard API configuration
  • • Teams needing Ghost Theme development (use Ghost Handlebars templating directly)

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes ↗
SDK
Yes
Webhooks
Yes
OpenAPI Spec ↗

Authentication

Methods: api_key
OAuth: No Scopes: Yes

Ghost Content API key (read-only public access) or Admin API key (full read/write). API keys generated in Ghost Admin panel under Integrations. Two separate APIs — Content API for reading, Admin API for writing.

Pricing

Model: freemium
Free tier: Yes
Requires CC: No

Ghost is open source — self-hosted is free. Ghost(Pro) managed hosting available at cost. MCP server is community open source and free.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Content API vs Admin API are separate with different keys and capabilities
  • ⚠ Ghost uses Lexical (or Mobiledoc legacy) for post content — not plain HTML or Markdown
  • ⚠ Members/newsletter features require Ghost with paid memberships enabled
  • ⚠ Self-hosted Ghost version matters — API features differ between Ghost 4 and Ghost 5
  • ⚠ Post status (draft/published/scheduled) must be set explicitly in API requests
  • ⚠ Community MCP server — may not cover full Ghost Admin API feature set

Alternatives

contentful-mcp-server sanity-mcp-server wordpress-mcp-server

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Ghost CMS MCP Server.

$99
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-06.

5215
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
♥
Community Powered