01 · Records and state owned
Spaces, stories, components, assets, users, roles, and supported Management API resources.
Storyblok
Storyblok
Curated major addition platform in headless cms with material relevance to the Marcom operating stack and a first-party developer surface.
Content, CMS, creative & DAMSystem of productionExtensible 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
Spaces, stories, components, assets, users, roles, and supported Management API resources.
03 · Actions and write paths
Read/write Management API operations, including content and asset administration, filtered by role/tool configuration.
04 · Authentication and permissions
Storyblok account/token authentication Storyblok roles and the server role parameter restrict exposed operations.
05 · Monitoring, approval, and recovery
Consequential writes should require explicit review; use vendor confirmation controls where available. Broad write scope makes least-privilege role configuration and explicit approval essential.
06 · Gaps and implementation limits
Broad write scope makes least-privilege role configuration and explicit approval essential.
First-party access
Documented surfaces
Storyblok GraphQL API ↗Storyblok provides GraphQL content queries through its delivery surface. Token, space, release, locale, schema, and cache behavior remain part of the access boundary.Source: Storyblok GraphQL APIMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP and adjacent posture
Verified first-party provider MCPStoryblok production-ready Content Management MCPProduction-ready documentation
Role: provider
Read scope: Spaces, stories, components, assets, users, roles, and supported Management API resources.
Write scope: Read/write Management API operations, including content and asset administration, filtered by role/tool configuration.
Authentication: Storyblok account/token authentication
Approval boundary: Consequential writes should require explicit review; use vendor confirmation controls where available.
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 access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed interfaces
What customers could build on top.
These are design proposals derived from documented access—not claims that Storyblok ships these experiences.
Single-platform patterns
- Component-based content and localization studio
- Campaign asset assembly room
- Brief-to-experience studio
- Content approval queue
Multi-platform compositions
- Storyblok + CRM or campaign platform: campaign asset assembly room
- Storyblok + 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
MCP / agent-role validationRepresentative source
https://www.storyblok.com/lp/mcp-server ↗Storyblok describes a production-ready server with broad Management API access and discovery-first operation filtering.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://www.storyblok.com/docs/api/content-delivery/v2 ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://www.storyblok.com/docs ↗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.
Webhooks / extensionsSource inventory
https://www.storyblok.com/docs/guide/in-depth/webhooks ↗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.
HomepageSource inventory
https://www.storyblok.com/ ↗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.
Storyblok GraphQL APITargeted review
Storyblok GraphQL API ↗Storyblok provides GraphQL content queries through its delivery surface. Token, space, release, locale, schema, and cache behavior remain part of the access boundary.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Targeted first-party access review
Verified fact
Tied to the representative first-party source or targeted access review.
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.