Storyblok MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.