What can Storyblok do?

storyblok space and story management via mcp protocol, component schema introspection and validation, asset management and media library access, workflow and publishing state management, multi-space and cross-space content discovery, real-time content synchronization and change detection, content versioning and rollback management, batch content operations and bulk updates

Storyblok

MCP ServerFree

** - Storyblok MCP server enables your AI assistants to directly access and manage your Storyblok spaces, stories, components, assets, workflows, and more.

Open Source

/ 100

8 capabilities

Capabilities8 decomposed

storyblok space and story management via mcp protocol

Medium confidence

Enables AI assistants to read, create, update, and delete stories within Storyblok spaces through the Model Context Protocol (MCP) interface. Implements MCP server endpoints that translate natural language requests into Storyblok REST API calls, handling authentication via API tokens and managing story metadata, content blocks, and publishing state without requiring direct API knowledge from the AI client.

Solves for

I want my AI assistant to create new stories in my Storyblok space based on user inputI need to update existing story content programmatically through an AI interfaceI want to retrieve story metadata and content for analysis or transformationI need to delete or archive stories through an AI-driven workflow

Best for

Content teams using Storyblok who want AI-assisted content creation and management

Developers building AI agents that need headless CMS integration

Teams automating content workflows with LLM-based decision making

Requires

Storyblok account with at least one space created

Valid Storyblok API token (Personal Access Token or OAuth token)

MCP-compatible AI client (Claude, or custom MCP host)

Limitations

MCP protocol overhead adds ~100-200ms per request compared to direct REST API calls

No built-in caching of story data — each request fetches fresh data from Storyblok

Requires Storyblok API token with appropriate space permissions; no fine-grained role-based access control at MCP layer

What makes it unique

Implements MCP server pattern specifically for Storyblok, allowing AI assistants to treat content management as a native capability rather than requiring custom API wrapper code. Uses MCP's standardized tool definition format to expose Storyblok operations, enabling any MCP-compatible client to manage content without Storyblok-specific knowledge.

vs alternatives

Provides direct MCP integration for Storyblok whereas most alternatives require building custom API wrappers or using generic REST client tools, reducing integration complexity for AI agents.

component schema introspection and validation

Medium confidence

Retrieves and exposes Storyblok component definitions (schemas) through MCP tools, allowing AI assistants to understand the structure of available content components before creating or updating stories. Parses component field definitions including field types, validation rules, and nested component relationships, enabling the AI to generate structurally valid content blocks without trial-and-error.

Solves for

I want my AI to know what fields and component types are available in my Storyblok spaceI need the AI to validate content structure before creating stories to avoid API errorsI want to understand component nesting rules so the AI creates valid component hierarchiesI need to expose component field constraints (required fields, field types) to the AI

Best for

Content teams with complex component hierarchies who need AI-aware content generation

Developers building AI content assistants that must respect schema constraints

Organizations migrating content workflows to AI-assisted processes

Requires

Storyblok space with at least one component defined

API token with read access to component definitions

MCP client capable of handling nested JSON schema responses

Limitations

Schema introspection is read-only; cannot modify component definitions through MCP

No real-time schema change detection — AI sees schema state at query time, not live updates

Complex nested component relationships may require multiple schema queries to fully resolve

What makes it unique

Exposes Storyblok's component schema as queryable MCP tools, enabling AI assistants to dynamically understand content structure without hardcoding schema knowledge. This allows the AI to adapt to schema changes without code updates and to generate valid content blocks by consulting the schema before creation.

vs alternatives

Unlike generic CMS integrations that treat components as opaque data, this capability makes component structure explicit and queryable to the AI, reducing invalid API calls and enabling schema-aware content generation.

asset management and media library access

Medium confidence

Provides MCP tools to list, upload, and reference assets (images, videos, documents) from Storyblok's asset library. Handles asset metadata retrieval, URL generation, and asset folder organization, allowing AI assistants to select appropriate media for stories or upload new assets programmatically while respecting Storyblok's asset naming and organization conventions.

Solves for

I want the AI to select and reference existing images from my asset library when creating storiesI need to upload new images or media files through the AI assistantI want the AI to organize assets into folders based on content type or campaignI need to retrieve asset URLs and metadata for content composition

Best for

Content teams managing large media libraries who want AI-assisted asset selection

Developers building AI content creation tools that need media integration

Organizations with automated content pipelines requiring asset management

Requires

Storyblok space with asset library enabled

API token with asset read/write permissions

For uploads: file access and appropriate MIME type support

Limitations

Asset upload through MCP may have file size limits depending on Storyblok plan and network constraints

No built-in image transformation or optimization — AI must reference assets as-is

Asset folder structure is read-only through MCP; folder creation/management not exposed

What makes it unique

Integrates Storyblok's asset library as queryable and writable MCP tools, enabling AI assistants to treat media selection and upload as first-class operations. Abstracts Storyblok's asset API complexity behind simple MCP tool calls, allowing AI to manage media without understanding Storyblok's asset folder structure or CDN URL patterns.

vs alternatives

Provides direct asset library integration through MCP whereas alternatives typically require separate media management workflows or manual asset linking, enabling end-to-end AI-driven content creation with media.

workflow and publishing state management

Medium confidence

Exposes Storyblok's workflow and publishing features through MCP tools, allowing AI assistants to transition stories through workflow stages (draft, in-review, published) and manage publication scheduling. Implements workflow state queries and transitions that respect Storyblok's configured workflow rules, enabling AI to orchestrate content through approval processes or schedule content publication.

Solves for

I want the AI to move stories through my approval workflow automaticallyI need to schedule story publication for specific dates/times through the AII want the AI to check if a story is ready for publication based on workflow stateI need to manage draft vs published versions of stories through AI commands

Best for

Content teams with multi-stage approval workflows who want AI-assisted workflow orchestration

Developers building AI content schedulers and publication pipelines

Organizations automating content release management

Requires

Storyblok space with workflows configured

API token with publish/workflow management permissions

Understanding of the space's configured workflow stages

Limitations

Workflow transitions must respect Storyblok's configured workflow rules; AI cannot bypass approval stages

Publishing scheduling depends on Storyblok's native scheduling capabilities and timezone handling

No webhook integration for workflow state changes — AI must poll for status updates

What makes it unique

Exposes Storyblok's workflow engine as MCP tools, enabling AI assistants to understand and execute workflow transitions without hardcoding workflow logic. Respects Storyblok's configured workflow rules and permissions, ensuring AI-driven workflows comply with organizational content governance.

vs alternatives

Provides workflow-aware publishing through MCP whereas generic CMS integrations treat publishing as a simple state toggle, enabling AI to orchestrate complex approval workflows and respect organizational content governance rules.

multi-space and cross-space content discovery

Medium confidence

Enables AI assistants to query and navigate across multiple Storyblok spaces within an organization, discovering stories, components, and assets across spaces. Implements space enumeration and cross-space search capabilities, allowing AI to find relevant content across the organization's content infrastructure and reference or copy content between spaces when needed.

Solves for

I want the AI to search for similar content across all my Storyblok spacesI need to discover what content exists in other spaces for reuse or referenceI want the AI to copy or migrate content between spacesI need to understand the organization's content structure across multiple spaces

Best for

Large organizations with multiple Storyblok spaces who need cross-space content discovery

Developers building AI content management dashboards for multi-space organizations

Teams managing content across multiple brands or regions

Requires

Multiple Storyblok spaces in the same organization

API token with access to all spaces being queried

Organization-level API token or multiple space-level tokens

Limitations

Cross-space queries require separate API calls per space; no built-in federation or aggregation

Content copying between spaces may require schema alignment if components differ

API token must have access to all spaces being queried; no per-space token scoping through MCP

What makes it unique

Implements cross-space content discovery as MCP tools, enabling AI to treat multiple Storyblok spaces as a unified content graph rather than isolated silos. Allows AI to discover, reference, and migrate content across organizational boundaries without requiring separate API clients per space.

vs alternatives

Provides multi-space awareness through MCP whereas typical Storyblok integrations focus on single-space operations, enabling AI to leverage content across the organization and discover reusable components and stories.

real-time content synchronization and change detection

Medium confidence

Monitors Storyblok spaces for content changes (story updates, asset uploads, component modifications) and exposes change events through MCP, enabling AI assistants to react to content updates in real-time. Implements polling or webhook-based change detection that tracks story versions, asset modifications, and component schema changes, allowing AI to trigger downstream workflows or regenerate dependent content.

Solves for

I want the AI to detect when stories are updated and trigger regeneration of dependent contentI need to monitor asset uploads and automatically process new mediaI want the AI to track component schema changes and alert on breaking changesI need to implement real-time content synchronization between Storyblok and external systems

Best for

Content teams with complex content dependencies who need AI-driven change propagation

Developers building real-time content synchronization pipelines

Organizations automating content workflows based on change events

Requires

Storyblok space with content to monitor

API token with read access to story versions and change history

MCP client capable of handling streaming or polling updates

Limitations

Polling-based change detection introduces latency (typically 5-60 seconds depending on poll interval)

No native webhook support through MCP — requires external webhook handler or polling fallback

Change history is limited to Storyblok's retention policy; older changes may not be queryable

What makes it unique

Exposes Storyblok change events as MCP tools, enabling AI assistants to react to content updates without polling or external webhook infrastructure. Allows AI to implement event-driven workflows where content changes trigger downstream processing or regeneration.

vs alternatives

Provides change detection through MCP whereas alternatives typically require external webhook handlers or manual polling, enabling AI to implement reactive content workflows without additional infrastructure.

content versioning and rollback management

Medium confidence

Provides MCP tools to query story version history, compare versions, and rollback to previous versions when needed. Implements version enumeration and diff capabilities that expose Storyblok's native versioning system, allowing AI assistants to understand content evolution and restore previous versions without manual intervention.

Solves for

I want the AI to show me what changed between story versionsI need to rollback a story to a previous version if recent changes are problematicI want the AI to compare content across versions for quality assuranceI need to understand the history of changes to a story for audit purposes

Best for

Content teams needing version control and rollback capabilities for AI-generated content

Developers building AI content editors with undo/redo functionality

Organizations requiring content audit trails and change tracking

Requires

Storyblok space with versioning enabled

API token with read access to version history

For rollback: API token with write permissions

Limitations

Version history retention depends on Storyblok plan; older versions may be purged

Rollback operations create new versions rather than reverting to exact historical state

Version comparison is at story level; field-level diffs require additional processing

What makes it unique

Exposes Storyblok's native versioning system as MCP tools, enabling AI assistants to understand and manage content history without requiring external version control systems. Allows AI to make informed decisions about content changes by comparing versions and rolling back when needed.

vs alternatives

Provides version-aware content management through MCP whereas alternatives typically treat content as stateless, enabling AI to implement quality assurance workflows with rollback capabilities.

batch content operations and bulk updates

Medium confidence

Enables AI assistants to perform bulk operations on multiple stories simultaneously (batch updates, bulk deletes, mass publishing) through MCP tools that handle transaction-like semantics. Implements batch operation queuing and error handling that allows AI to modify large content sets efficiently while maintaining consistency and providing detailed operation reports.

Solves for

I want the AI to update multiple stories at once based on a pattern or criteriaI need to bulk publish stories that meet certain conditionsI want to perform mass content migrations or transformationsI need detailed reports on which stories succeeded or failed in batch operations

Best for

Content teams managing large content libraries who need AI-driven bulk operations

Developers building AI content migration and transformation tools

Organizations automating large-scale content updates

Requires

Storyblok space with multiple stories

API token with write permissions for bulk operations

MCP client capable of handling long-running operations

Limitations

Batch operations are subject to API rate limits; large batches may require throttling

No true transactions — partial failures may leave content in inconsistent state

Batch size limits depend on Storyblok API constraints; very large batches may need splitting

What makes it unique

Implements batch operation tools that allow AI to perform efficient bulk updates while handling errors and providing detailed operation reports. Abstracts the complexity of managing multiple concurrent API calls and error handling, enabling AI to treat bulk operations as atomic MCP tools.

vs alternatives

Provides batch operation support through MCP whereas alternatives typically require sequential individual API calls, enabling AI to perform large-scale content updates efficiently with built-in error handling and reporting.

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with Storyblok, ranked by overlap. Discovered automatically through the match graph.

MCP Server29

storybook-mcp-server

MCP server for Storybook - provides AI assistants access to components, stories, properties and screenshots

component-metadata-extraction-and-indexingmcp-tool-exposure-for-ai-assistantsstory-argument-schema-generationstory-metadata-and-documentation-indexing

4 shared capabilities

MCP Server28

@superblocksteam/mcp-server

Superblocks MCP server

mcp resource and prompt template exposuresuperblocks authentication and credential management for mcpsuperblocks workflow tool registration and discovery

3 shared capabilities

Product38

Builder.io

AI visual development with design-to-code and CMS.

headless cms with content-to-component bindingstorybook integration and story generation

2 shared capabilities

MCP Server26

Agile Luminary

** - Simpler Project Management - send [Agile Luminary](https://agileluminary.com) stories straight to your IDE

mcp-based project management story synchronizationstory status and metadata querying via mcp tools

2 shared capabilities

Agent56

sim

Build, deploy, and orchestrate AI agents. Sim is the central intelligence layer for your AI workforce.

block-based tool registry with dynamic schema enrichment

1 shared capability

Product29

Deep Realms

Unleash AI-driven storytelling, character creation, and collaborative...

project organization and content management

1 shared capability

Best For

✓Content teams using Storyblok who want AI-assisted content creation and management
✓Developers building AI agents that need headless CMS integration
✓Teams automating content workflows with LLM-based decision making
✓Content teams with complex component hierarchies who need AI-aware content generation
✓Developers building AI content assistants that must respect schema constraints
✓Organizations migrating content workflows to AI-assisted processes
✓Content teams managing large media libraries who want AI-assisted asset selection
✓Developers building AI content creation tools that need media integration

Known Limitations

⚠MCP protocol overhead adds ~100-200ms per request compared to direct REST API calls
⚠No built-in caching of story data — each request fetches fresh data from Storyblok
⚠Requires Storyblok API token with appropriate space permissions; no fine-grained role-based access control at MCP layer
⚠Story versioning and draft/published state management depends on Storyblok's native capabilities
⚠Schema introspection is read-only; cannot modify component definitions through MCP
⚠No real-time schema change detection — AI sees schema state at query time, not live updates

Requirements

Storyblok account with at least one space createdValid Storyblok API token (Personal Access Token or OAuth token)MCP-compatible AI client (Claude, or custom MCP host)Network access to Storyblok API endpoints (api.storyblok.com)Storyblok space with at least one component definedAPI token with read access to component definitionsMCP client capable of handling nested JSON schema responsesStoryblok space with asset library enabled

Input / Output

Accepts: structured JSON (story objects with name, slug, content, component definitions), text (story titles, descriptions, content blocks), identifiers (story IDs, space IDs, component names), component names (strings), space identifiers, asset identifiers (IDs, names), file data (binary for uploads), folder paths (strings), search queries (text), story identifiers, workflow stage names (strings), publication timestamps (ISO 8601 format), publish scope (draft, published), content type filters, change type filters (story, asset, component), time range queries, version numbers or timestamps, comparison parameters, story identifiers (arrays), update payloads (JSON), filter criteria (for bulk selection), operation type (update, delete, publish)

Produces: structured JSON (story metadata, content, publishing status), text (confirmation messages, error details), boolean (success/failure indicators), structured JSON (component schema with field definitions, types, validation rules), text (human-readable component documentation), structured JSON (asset metadata, URLs, folder structure), text (asset names, descriptions), URLs (CDN links to assets), structured JSON (workflow state, publication status, scheduled dates), text (workflow stage names, status messages), boolean (publication eligibility), structured JSON (stories, components, assets across spaces), text (search results, space listings), aggregated metadata, structured JSON (change events with timestamps, change types, affected resources), text (change summaries, notifications), event streams, structured JSON (version metadata, diffs, change summaries), text (version descriptions, change logs), boolean (rollback success), structured JSON (operation results, success/failure counts, detailed error logs), text (operation summaries, progress reports), batch operation status

UnfragileRank

Adoption15%(30% weight)

Quality25%(25% weight)

Ecosystem30%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

8 capabilities

Visit Storyblok→

About

** - Storyblok MCP server enables your AI assistants to directly access and manage your Storyblok spaces, stories, components, assets, workflows, and more.

Alternatives to Storyblok

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of Storyblok?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

github awesome

Looking for something else?

Search →

Capabilities8 decomposed

storyblok space and story management via mcp protocol

Medium confidence

Solves for

Best for

Content teams using Storyblok who want AI-assisted content creation and management

Developers building AI agents that need headless CMS integration

Teams automating content workflows with LLM-based decision making

Requires

Storyblok account with at least one space created

Valid Storyblok API token (Personal Access Token or OAuth token)

MCP-compatible AI client (Claude, or custom MCP host)

Limitations

MCP protocol overhead adds ~100-200ms per request compared to direct REST API calls

No built-in caching of story data — each request fetches fresh data from Storyblok

Requires Storyblok API token with appropriate space permissions; no fine-grained role-based access control at MCP layer

What makes it unique

vs alternatives

Provides direct MCP integration for Storyblok whereas most alternatives require building custom API wrappers or using generic REST client tools, reducing integration complexity for AI agents.

component schema introspection and validation

Medium confidence

Solves for

Best for

Content teams with complex component hierarchies who need AI-aware content generation

Developers building AI content assistants that must respect schema constraints

Organizations migrating content workflows to AI-assisted processes

Requires

Storyblok space with at least one component defined

API token with read access to component definitions

MCP client capable of handling nested JSON schema responses

Limitations

Schema introspection is read-only; cannot modify component definitions through MCP

No real-time schema change detection — AI sees schema state at query time, not live updates

Complex nested component relationships may require multiple schema queries to fully resolve

What makes it unique

vs alternatives

asset management and media library access

Medium confidence

Solves for

Best for

Content teams managing large media libraries who want AI-assisted asset selection

Developers building AI content creation tools that need media integration

Organizations with automated content pipelines requiring asset management

Requires

Storyblok space with asset library enabled

API token with asset read/write permissions

For uploads: file access and appropriate MIME type support

Limitations

Asset upload through MCP may have file size limits depending on Storyblok plan and network constraints

No built-in image transformation or optimization — AI must reference assets as-is

Asset folder structure is read-only through MCP; folder creation/management not exposed

What makes it unique

vs alternatives

workflow and publishing state management

Medium confidence

Solves for

Best for

Content teams with multi-stage approval workflows who want AI-assisted workflow orchestration

Developers building AI content schedulers and publication pipelines

Organizations automating content release management

Requires

Storyblok space with workflows configured

API token with publish/workflow management permissions

Understanding of the space's configured workflow stages

Limitations

Workflow transitions must respect Storyblok's configured workflow rules; AI cannot bypass approval stages

Publishing scheduling depends on Storyblok's native scheduling capabilities and timezone handling

No webhook integration for workflow state changes — AI must poll for status updates

What makes it unique

vs alternatives

multi-space and cross-space content discovery

Medium confidence

Solves for

Best for

Large organizations with multiple Storyblok spaces who need cross-space content discovery

Developers building AI content management dashboards for multi-space organizations

Teams managing content across multiple brands or regions

Requires

Multiple Storyblok spaces in the same organization

API token with access to all spaces being queried

Organization-level API token or multiple space-level tokens

Limitations

Cross-space queries require separate API calls per space; no built-in federation or aggregation

Content copying between spaces may require schema alignment if components differ

API token must have access to all spaces being queried; no per-space token scoping through MCP

What makes it unique

vs alternatives

real-time content synchronization and change detection

Medium confidence

Solves for

Best for

Content teams with complex content dependencies who need AI-driven change propagation

Developers building real-time content synchronization pipelines

Organizations automating content workflows based on change events

Requires

Storyblok space with content to monitor

API token with read access to story versions and change history

MCP client capable of handling streaming or polling updates

Limitations

Polling-based change detection introduces latency (typically 5-60 seconds depending on poll interval)

No native webhook support through MCP — requires external webhook handler or polling fallback

Change history is limited to Storyblok's retention policy; older changes may not be queryable

What makes it unique

vs alternatives

content versioning and rollback management

Medium confidence

Solves for

Best for

Content teams needing version control and rollback capabilities for AI-generated content

Developers building AI content editors with undo/redo functionality

Organizations requiring content audit trails and change tracking

Requires

Storyblok space with versioning enabled

API token with read access to version history

For rollback: API token with write permissions

Limitations

Version history retention depends on Storyblok plan; older versions may be purged

Rollback operations create new versions rather than reverting to exact historical state

Version comparison is at story level; field-level diffs require additional processing

What makes it unique

vs alternatives

Provides version-aware content management through MCP whereas alternatives typically treat content as stateless, enabling AI to implement quality assurance workflows with rollback capabilities.

batch content operations and bulk updates

Medium confidence

Solves for

Best for

Content teams managing large content libraries who need AI-driven bulk operations

Developers building AI content migration and transformation tools

Organizations automating large-scale content updates

Requires

Storyblok space with multiple stories

API token with write permissions for bulk operations

MCP client capable of handling long-running operations

Limitations

Batch operations are subject to API rate limits; large batches may require throttling

No true transactions — partial failures may leave content in inconsistent state

Batch size limits depend on Storyblok API constraints; very large batches may need splitting

What makes it unique

vs alternatives

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to Storyblok

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Storyblok

Capabilities8 decomposed

storyblok space and story management via mcp protocol

component schema introspection and validation

asset management and media library access

workflow and publishing state management

multi-space and cross-space content discovery

real-time content synchronization and change detection

content versioning and rollback management

batch content operations and bulk updates

Related Artifactssharing capabilities

storybook-mcp-server

@superblocksteam/mcp-server

Builder.io

Agile Luminary

sim

Deep Realms

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Storyblok

Are you the builder of Storyblok?

Get the weekly brief

Data Sources

Storyblok

Capabilities8 decomposed

storyblok space and story management via mcp protocol

component schema introspection and validation

asset management and media library access

workflow and publishing state management

multi-space and cross-space content discovery

real-time content synchronization and change detection

content versioning and rollback management

batch content operations and bulk updates

Related Artifactssharing capabilities

storybook-mcp-server

@superblocksteam/mcp-server

Builder.io

Agile Luminary

sim

Deep Realms

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to Storyblok

Are you the builder of Storyblok?

Get the weekly brief

Data Sources