Storyblok MCP Server
Related Servers
Alternatives to Storyblok MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityNot gradedmaintenanceAn MCP server that enables AI assistants like Cursor and Claude to interact with the Storyblok Management API. It allows users to manage stories, tags, components, assets, and workflows through natural language commands.7443 npm-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to browse Storybook components, manage stories, inspect props, and capture screenshots of components.211 npm14AGPL 3.0
- AlicenseCqualityDmaintenanceA Storyblok MCP Server built on TypeScript with more than 130+ Actions1008MIT

Storyblok MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceProvides access to the Storyblok Management API via MCP, enabling content management and operations on Storyblok spaces through natural language. Note: This repository is archived; use the hosted version at mcp.labs.storyblok.com.43 npm8MIT- FlicenseNot gradedqualityDmaintenanceA comprehensive server enabling natural language interaction with Storyblok CMS for managing stories, assets, components, releases, and other content through a modular architecture.3 npm1-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive management of Storyblok CMS through natural language interactions. Supports story creation and publishing, asset management, component schema updates, release workflows, and content discovery across all major Storyblok APIs.3 npm-
TDQS
Scored across 160 tools
Most tools are clearly distinct with specific resource-action pairs (e.g., create_story vs. update_story), but there is some potential confusion between similar retrieval tools like retrieve_single_activity and retrieve_multiple_activities, or between create_approval and create_release_approval. The descriptions help clarify, but the sheer number of tools creates some cognitive overlap.
Naming is highly consistent throughout, following a clear verb_noun pattern (e.g., create_story, update_story, delete_story) with predictable variations for bulk operations (bulk_create_stories) and retrieval types (retrieve_single_*, retrieve_multiple_*, fetch_*). The pattern is maintained across all 160 tools without deviation.
With 160 tools, the count is excessive for a single server, even for a comprehensive CMS like Storyblok. This volume will overwhelm agents, making tool selection difficult and inefficient. A more focused or modular approach would be more appropriate for the domain.
The tool set provides exhaustive coverage of the Storyblok domain, including full CRUD operations for stories, assets, components, spaces, workflows, releases, and more, plus advanced features like translations, backups, approvals, and validations. No obvious gaps are present; it supports complete lifecycle management.