01 · Records and state owned
Spaces, stories, components, assets, users, roles, and supported Management API resources.
Storyblok
Storyblok
Storyblok exposes its Management API through discovery-first MCP tools that separate reads, recoverable mutations, destructive operations, and a dedicated asset-upload flow.
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
Discover Management API operations, inspect their schemas, and execute GET operations for permitted stories, components, assets, spaces, users, roles, and other exposed resources.
03 · Actions and write paths
Execute permitted POST, PUT, and PATCH operations for content management and publishing; route DELETE operations separately; create and finalize assets through the specialized upload flow.
04 · Authentication and permissions
The hosted server accepts a Storyblok Personal Access Token as a bearer credential. Scoped personal access tokens restrict API access by resource type; the former role query parameter is deprecated.
05 · Monitoring, approval, and recovery
The server separates GET, mutating, and destructive execution tools, requires schema description before execution, and requires explicit user confirmation for destructive calls.
06 · Limits and caveats
Storyblok labels this an experimental Labs research project that may change without notice; Labs features are beta. Its discovery layer exposes broad Management API reach.
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 support
Official MCP serverStoryblok-hosted experimental Labs MCP over the Management APIExperimental Storyblok Labs beta
Support: Official MCP server
Read scope: Expose only scoped-token GET operations, with operation schema, region, space, pagination, selected fields, publication status, and unpublished-change state visible in the result.
Write scope: Keep create, update, and publish operations separate from delete or purge. Asset uploads also require an external signed-upload step followed by finalization.
Authentication: Connect to the stateless hosted endpoint with a Storyblok Personal Access Token, also called a Management Token, supplied as a bearer header.
Approval boundary: Confirm operation ID, region, space, story or asset target, schema-resolved parameters, draft-versus-publish intent, and payload before mutation; require fresh explicit confirmation for deletion or purge.
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 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 Storyblok ships them.
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 12, 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.
Developer docsSource inventory
https://www.storyblok.com/docs/api/graphql ↗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.
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.
Webhooks / extensionsSource inventory
https://www.storyblok.com/docs/concepts/webhooks.html ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- 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.
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.