Can AI Edit or Publish to Your Ghost Site?

Yes, through Ghost's Admin API, not through a public chat conversation. Ghost's own built-in AI feature is about being found by AI tools, not editing your site with one. For an agent to actually draft, edit, or publish content, it needs a credential: either a Custom Integration's Admin API key, which is limited to a fixed set of endpoints, or a staff access token, which inherits whatever a specific staff user's role can do. Which one you hand an agent decides how much of your site it can reach.

What does Ghost's own built-in AI do?

Ghost's built-in AI feature, shipped July 16, 2026, is aimed at AI search rather than editing: built-in GEO tools that generate the files AI systems look for and serve Markdown versions of your public content, toggled on in Settings → Meta data (Ghost Changelog, "Optimize your site for AI search", July 16, 2026). Once enabled, Ghost publishes an llms.txt file at your domain's root and serves a Markdown version of any post when you append .md to its URL — the same mechanism that renders ghost.org/changelog/geo.md. Only public content is included; "Members-only and paid posts are listed with their public title and excerpt, but their protected content is not," and private sites don't serve these files at all (same source).

This is off by default for existing sites — "this feature is off by default for existing sites... there's nothing you need to do; it will remain switched off" unless you turn it on. Ghost(Pro) users get it immediately; "if you're a developer, self-hosting Ghost, you'll need to update to the latest version to get access to everything that's new" (same source). Ghost does not publish a separate in-editor writing assistant or design-generation AI as of this check; its own AI feature is specifically this discoverability layer.

Can an outside AI agent edit my existing Ghost site?

Yes, through the Admin API — there is no official Ghost MCP server, so a scoped API key is the real route. Ghost's developer docs describe two ways an agent authenticates: integration tokens, meant for integrations that handle common workflows such as publishing content, and staff access tokens, meant for people who act as themselves without sharing a password (Ghost Developer Docs, Admin API, checked September 2026).

The two routes reach different amounts of the site:

• Custom Integration (Admin API key). Created from Settings → Integrations → Add custom integration in Ghost Admin: "Admin API keys can be obtained by creating a new Custom Integration under the Integrations screen in Ghost Admin" (same source). This is the scoped route: "Integrations have a restricted set of fixed permissions allowing access to certain endpoints e.g. GET /users/ or POST /posts/" — a fixed, documented set, not a full user's permissions.
• Staff access token. Found on a specific staff user's own profile page. "User permissions (whether using staff tokens or user authentication) are dependent entirely on their role... Authenticating as a user with the Owner or Admin role will give access to the full set of API endpoints." Ghost's docs add one hard limit that applies even at the top role: "Staff tokens cannot transfer ownership or delete all content" (same source).

If you're looking for a Ghost MCP server: Ghost does not publish one. Community-built MCP servers exist that wrap the Admin API for MCP clients like Claude, but they are third-party tools, not something Ghost documents or maintains — treat them like any other unofficial integration and review what scope of key you hand them.

What can an agent actually publish, and what can't it?

Give the agent a staff account with the lowest role that can do its job, not your Owner login. Ghost's help center lists four staff roles with a specific permission breakdown (Ghost, "What permissions do staff users have?", checked September 2026):

A Contributor is the safest role for an agent that drafts content for you to review and publish yourself — it can create and edit its own drafts but cannot publish them or touch anyone else's content. An Author is the lowest role that can publish on its own, appropriate only once you trust the agent's output without a human gate. Neither role can change site settings, themes, or other users, regardless of what credential reaches it.

Does self-hosted vs Ghost(Pro) change what an agent can do?

No — the Admin API and staff roles work the same either way. Ghost's own hosting guide states the product is identical across both: "Product features: Identical, Identical" between Ghost(Pro) and self-hosting (Ghost Developer Docs, "Hosting Ghost", checked September 2026). What differs is who manages the infrastructure around it: Ghost(Pro) bundles services such as email delivery and full site backups, while a self-hosted install sources those separately (same source). The practical difference for an AI-agent workflow: a self-hosted install has to be updated manually to receive new features like GEO, while Ghost(Pro) gets them automatically.

What's a safe setup checklist?

1. Decide the job. Drafting new posts from source material is different from bulk-editing tags across hundreds of existing posts — the second is a much bigger blast radius.
2. Create a Custom Integration, not a personal staff token, when the job is narrow. Settings → Integrations → Add custom integration gives you an Admin API key scoped to the fixed set of endpoints Ghost documents, independent of any human user's account.
3. Use a Contributor-role staff account instead when the agent needs to work inside the normal editor UI — drafts only, nothing published without your review.
4. Regenerate the key when the task is done. "You can regenerate the Admin API key any time, but any scripts or applications using it will need to be updated" — there's no separate revoke step, so regenerating invalidates the old key immediately.
5. Check the live post. Preview before publishing, then open the public URL and confirm formatting, images, and any newsletter send behaved as expected.

What's the recovery path if something goes wrong?

Ghost's own export is the backup. From Settings → Advanced → Import/Export, exporting produces "a single JSON file" containing "All Settings, Staff users, Posts, Pages, Tags, Members" (Ghost, "Exporting content and data", checked September 2026). Members also export separately as CSV with fields including subscription status and Stripe customer ID, and theme files download as a zip from Design & branding settings. Export this JSON file before letting an agent run a bulk operation across your content — it's the only way back if a scoped key does more than you intended within its permitted endpoints.

For the full builder-by-builder view of what's exportable, our export capability matrix covers Ghost alongside 15 other platforms. For the general question of what an AI agent can and can't do once it has access to any site, see how ChatGPT, Claude, Codex or Cursor can edit an existing website, and for the platform-by-platform version of the role-and-token question above, see how to give an AI agent access to your website without handing over your login.

Bottom line: Ghost's own AI feature makes your content easier for AI search tools to find, not easier for AI tools to edit. Editing goes through the Admin API — a scoped Custom Integration key for a narrow, fixed set of endpoints, or a staff access token that inherits a specific user's role. Ghost is a publishing and newsletter platform, not a page-design tool, so it isn't a fit for Figment's Figma-to-website workflow; the honest answer here is simply to use the right key for the job and keep a fresh JSON export before anything bulk runs.