Claude + Ghost: What the Integration Can (and Can't) Do in 2026
No official Claude Ghost connector — but there’s a well-maintained community MCP server, and it works. To be clear on which Ghost this is: Ghost is the open-source publishing platform and CMS (ghost.org), the one writers and newsletter operators run their sites on — not the fintech, the messaging app, or the browser tool of the same name. Ghost has no official Anthropic connector and no vendor-hosted MCP, but the community has shipped a strong, actively maintained local MCP server, and Ghost’s own self-serve API is one of the cleanest in this category. Both routes carry the usual Claude limit, though: they only work inside a conversation you start. Nothing watches your site, nothing fires when a post publishes, and nothing runs while you’re away.
Here’s exactly what’s available, how to turn it on, where the limits bite, and what to use if you want Ghost work that runs on its own.
What actually exists: a strong community MCP + a clean self-serve API
There’s no first-party Ghost MCP and nothing in Anthropic’s directory. But the community ecosystem is genuinely good — and, importantly, these servers use Ghost’s official APIs, so they’re not reverse-engineered or ToS-risky.
The standout is MFYDev/ghost-mcp (~210 stars, TypeScript, latest v0.2.0 in April 2026). It’s a local (stdio) server you run via npx in your Claude Desktop config. It authenticates with a Ghost Admin API key (converted to a JWT via @tryghost/admin-api) and manages posts, users, members, tiers, offers, and newsletters. Other maintained options include mtane0412/ghost-mcp-server, workspace/ghost-mcp, and hithereiamaliff/mcp-ghostcms — all built on Ghost’s APIs, all self-hosted/local rather than a hosted OAuth endpoint.
Under all of them sits Ghost’s self-serve API, which is best-in-class for this group:
- Content API — read-only, simple API key.
- Admin API — full CRUD; the key is an
id:secretpair used to sign short-lived JWTs. - Setup is instant. Any user creates a Custom Integration in Ghost Admin and immediately gets both Content and Admin keys — copied the moment the integration is created. No approval gating, on both self-hosted Ghost and Ghost(Pro).
- Webhooks: yes — created via the Admin API (
POST /admin/webhooks/) or the Ghost Admin UI by picking a trigger event and target URL. (There’s no endpoint to list existing webhooks, worth knowing.)
How to set up the community MCP
Using MFYDev/ghost-mcp with Claude Desktop:
- In Ghost Admin → Settings → Integrations, create a Custom Integration and copy the Admin API key and your site URL.
- Add
ghost-mcpto your Claude Desktop MCP config (it runs vianpx), passing the Admin API key and URL as environment variables per the repo’s README. - Restart Claude Desktop, then ask Claude to draft a post, list members, or update a newsletter — it’ll call Ghost’s Admin API through the server.
Because these are local (stdio) servers, they run in Claude Desktop or Claude Code — not the claude.ai web app. Adding custom MCP connectors requires a paid Claude plan.
The limits that actually matter
The community MCP is good at pulling Ghost into a conversation. But its shape is “an assistant you operate,” not “an agent that runs.” Three limits define it:
- No triggers, no monitoring. The server only works inside a conversation you start. There’s no “when a member signs up, send a welcome note” or “publish this draft every Thursday at 8am.” Nothing fires on a Ghost event — you have to be there, prompting.
- Conversation-only. Claude drafts and edits when you ask; it doesn’t sit watching new members or comments and acting on them. Close the chat and nothing continues.
- Laptop-bound. These are local servers, and the nearest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. That’s not an always-on publishing agent.
So Claude is great for “draft this post and clean up the tags right now” and not built for “publish on a schedule and welcome every new member.”
If you want Ghost work that runs on its own: Carly
The moment you want something to happen around Ghost without you in the chat — publish a queued draft on a schedule, welcome a new member the instant they subscribe, repurpose each new post into a social summary, email yourself a weekly member roll-up — you’ve crossed past what the community MCP is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud — using Ghost’s webhooks, when a post publishes or a member joins, Carly acts; your laptop doesn’t need to be awake.
- Connects Ghost to the rest of your stack — turn a new post into an email draft, add a new member to your CRM, or drop subscriber numbers into a Sheet as one workflow.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, updates your CRM, and records meetings.
- Builds the workflow for you — tell it “I’d like a system that welcomes every new member and summarizes each new post for social” in plain English; it interviews you, then builds it with you. No prompt engineering.
Carly reaches Ghost through your own API key — create a Custom Integration in Ghost Admin and paste the Admin API key on carlyassistant.com/integrations. We take the key and can do whatever Ghost’s Admin and Content APIs allow. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations.
Claude vs Carly
| Claude (community MCP) | Carly | |
|---|---|---|
| Draft & edit posts | Yes | Yes |
| Manage members & newsletters | Yes | Yes |
| Works on claude.ai web | No (Desktop/Code only) | N/A (cloud service) |
| Acts on triggers / webhooks | No | Yes |
| Publishes on a schedule | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends email as part of the flow | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
The community MCP is a strong Ghost editor inside a desktop chat. Carly is a teammate that publishes, welcomes, and reports on its own.
Frequently Asked Questions
Does Claude work with Ghost?
Yes, through a community MCP server. There’s no official Claude Ghost connector and no vendor-hosted MCP, but the well-maintained MFYDev/ghost-mcp (~210 stars) is a local server that connects Claude Desktop to your Ghost site using an Admin API key. It manages posts, members, tiers, and newsletters. Like all MCP setups, it only works inside a conversation you start, and being local it runs in Claude Desktop/Code, not claude.ai web.
Does Ghost have an API?
Yes, and it’s excellent. Ghost splits it into a read-only Content API (simple key) and a full-CRUD Admin API (an id:secret key used to sign JWTs). You create a Custom Integration in Ghost Admin and get both keys instantly — no approval gating, on self-hosted Ghost or Ghost(Pro). Webhooks are supported via the Admin API or the Admin UI.
How do I connect Claude to Ghost?
Create a Custom Integration in Ghost Admin (Settings → Integrations) to get your Admin API key, then add a community server like ghost-mcp to your Claude Desktop MCP config with that key. Restart Claude Desktop and ask it to draft or manage posts. Custom MCP connectors require a paid Claude plan.
Can Claude publish or welcome members on a schedule?
No. The community MCP responds inside a chat and doesn’t act on Ghost events. For automatic, trigger- or schedule-based Ghost work — publishing drafts, welcoming members, repurposing posts — use an agent platform like Carly, which fires on Ghost’s webhooks 24/7 in the cloud. AI agents start at $35/month.
More: Claude connectors · Claude + WordPress · Claude + Substack · Can Claude send emails · Claude vs Carly · Best AI tools for solopreneurs
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
