No user-submitted related servers found.
Scored across 160 tools
Tools target distinct resources (stories, assets, components, etc.) with specific verbs, making them largely distinguishable. A few overlaps exist between 'get_*', 'fetch_*', and 'retrieve_single_*' functions, but these target different entities and are not ambiguous.
The naming pattern is predominantly verb_noun with snake_case, but there is inconsistency in verb choice: 'create' vs 'add', 'fetch' vs 'retrieve' vs 'get', and some tools have non-standard prefixes like 'ai_', 'debug_', 'bulk_', 'tag_bulk_association' (verb last). This reduces overall consistency.
With 160 tools, the surface is extremely large. While the server aims to cover the full Storyblok Management API, many tools could be consolidated into parameterized operations (e.g., merging 'retrieve_single_*' and 'retrieve_multiple_*' variants). The high count adds complexity and cognitive load for agents.
The server covers an impressive breadth of Storyblok features: spaces, stories, assets, components, datasources, workflows, approvals, releases, discussions, webhooks, and more. Basic CRUD operations are present for most entities. Minor gaps exist (e.g., no update_approval, no update_discussion), but core workflows are fully supported.