Read/write entries, content types and assets; manage content models, environments and selected AI Actions across approved spaces and environments
Contentful
Contentful gives agents governed access to structured content, models, assets, locales, taxonomy, and AI Actions across explicitly selected spaces and environments.
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.
Search and inspect entries, snapshots, content types, assets, spaces, environments, locales, tags, taxonomy, editor interfaces, organizations, and configured AI Actions.
Create, update, publish, unpublish, archive, restore, or delete content; evolve models and locales; upload assets; manage taxonomy and environments; and invoke AI Actions.
Remote access uses OAuth 2.1 and each user's Contentful identity, then applies the MCP app's environment-level tool and read/write allowlist. Local access inherits one PAT owner's authority.
Remote administrators choose tool categories and read-only or read/write access per environment; user permissions still apply. Contentful recommends human confirmation and beginning with read-only enablement.
Remote use requires the MCP app in every target environment; environment aliases are unsupported. Global and EU organizations must use their matching fixed endpoint.
First-party access
Documented surfaces
Agent access
MCP support
Support: Official MCP server
Read scope: Expose content, model, asset, locale, taxonomy, and environment reads only for session-selected spaces and environments, preserving version, publication state, locale, and reference context.
Write scope: Allow only enabled categories and modes. Publishing, unpublishing, archiving, deletion, model changes, locale changes, environment creation or deletion, and AI Action invocation change production state.
Authentication: The hosted server uses OAuth 2.1 with interactive Contentful sign-in and session scope selection. The local package instead receives a Content Management API personal access token.
Approval boundary: Confirm target space, environment, locale, current version, and intended state before publish, unpublish, archive, delete, model, environment, taxonomy, or AI Action operations.
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.
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 Contentful ships them.
Single-platform patterns
- Composable content and localization studio
- Campaign asset assembly room
- Brief-to-experience studio
- Content approval queue
Multi-platform compositions
- Contentful + CRM or campaign platform: campaign asset assembly room
- Contentful + work-management system + analytics or distribution platform: 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.
6 recorded sources
Remote OAuth 2.1 access has two-layer permission gating: Contentful user permissions plus per-space/environment allowlists through the MCP app. Local PAT mode lacks equivalent per-tool/per-environment gating and should…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party developer documentation or 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.
Reverified the named access facet exactly as bounded by the reviewed first-party record.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension 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.
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.