01 · Records and state owned
Posts, pages, tags, authors/users, members, tiers, newsletters, offers, labels, images, themes, site settings, and webhooks.
Ghost Foundation
Ghost
A widely used open publishing platform whose Admin API, Content API, role-aware authentication, integrations, and webhooks make it a strong foundation for customer-owned editorial experiences.
Publishing, newsletters & creator platformsSystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve content and authorized Admin resources using role-based user authentication or integration tokens.
03 · Actions and write paths
Create, update, schedule, publish, email, and delete posts/pages; manage members, newsletters, offers, themes, images, and webhooks where the credential permits.
04 · Authentication and permissions
Ghost supports integration JWTs, staff access tokens, or session-based user authentication. Integration permissions are fixed; staff and user access follows roles, with Admin or Owner reaching all documented endpoints.
05 · Monitoring, approval, and recovery
Integration and staff keys must remain server-side; use Ghost's version header, preserve role attribution for user access, and separately approve publication, email, theme activation, or member changes.
06 · Limits and caveats
Only third-party/community MCP was verified. Admin API writes can publish or email immediately and therefore require explicit review gates.
First-party access
Documented surfaces
Agent access
MCP support
Third-party onlyCommunity MCP only; official API/CLI available
Support: Third-party only
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Require explicit review before publishing or emailing content, changing member or tier state, activating themes, or modifying webhooks; integration credentials otherwise execute independently of a staff user.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Ghost Foundation ships them.
Single-platform patterns
- Editorial operating room for a Ghost publication
- Publication operator cockpit
- Editorial planning room
- Audience and membership explorer
Multi-platform compositions
- Ghost + video or creative platform: publication operator cockpit
- Ghost + social or distribution system + analytics or commerce system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
Admin APIRepresentative source
https://docs.ghost.org/admin-api ↗Admin resources and methods, versioning, integration and staff JWTs, user sessions, fixed integration permissions, and role-based user access
- Publisher updated
- Jun 1, 2026
- BYO-UI reviewed
- Jul 22, 2026
Ghost Admin API resources, authentication, permissions, and writes reviewed 2026-07-22
Content APISource inventory
https://docs.ghost.org/content-api ↗First-party read-only public-content API.
- Publisher updated
- Jan 26, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.ghost.org/ ↗First-party developer documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://ghost.org/ ↗Product and open-source platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
WebhooksSource inventory
https://docs.ghost.org/webhooks ↗First-party event configuration.
- Publisher updated
- Jan 26, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.