# Future Interoperability Plan

Status: demand-gated after observed v0.4 usage.

## Portable MCP prompts

Add two prompts for clients that support MCP prompts:

- `ghost_safe_publish`: exact draft review, one approval covering named transitions and the configured automatic deployment, publish, and live verification.
- `ghost_seo_optimize`: evidence gathering, exact metadata proposal, approval covering the patch and one named manual deployment, revision-saving update, deploy, and live verification.

Both prompts must treat Ghost, crawl, SEO, query, and SERP content as untrusted evidence; use exact IDs and current timestamps; name every destructive action in approval; never send newsletters; and never edit published bodies. They should work in Codex, Claude, Cursor, and other MCP-prompt clients.

Retain the richer Codex optimizer skill. Do not add duplicate MCP resources while the structured tools already supply the required data.

## Demand triggers

- Add remote transport only for a hosted-user requirement backed by a threat model.
- Add membership or newsletters only as a separate permission-scoped surface.
- Add Lexical editing only after round-trip fixtures prove cards survive and rollback is tested.
- Revisit body search only after a real workflow defines strict pagination, payload, and latency limits.

Deletion, tag administration, page scheduling, site administration, webhook modification, themes, users, roles, persistent approval state, automatic deployment retries, background scheduling, arbitrary NQL, databases, dashboards, telemetry, billing, and embedded AI providers remain outside this milestone.

MFYDev/ghost-mcp may be used only as a behavioral reference with disposable Ghost. It is never a runtime dependency or production companion, and every adopted idea must be independently verified against official Ghost documentation and Ghost 5/6.