Storyblok MCP Server
Summary: It is an MCP server that gives AI assistants programmatic, typed access to Storyblok Management API content, workflow, and configuration operations.
Manage Storyblok content and schema objects: stories, components, assets, tags, internal tags, datasources, entries, presets, and component usage/versions.
Configure workflows and approvals: workflows, stages, stage changes, approvals, releases, story schedules, branches, and deployments.
Administer spaces and permissions: spaces, access tokens, collaborators, space roles, and activity logs.
Manage webhooks and tasks.
Check server/API health and list available tool categories.
Provides comprehensive access to the Storyblok Management API, enabling AI agents to manage stories, components, assets, workflows, releases, datasources, and team collaboration.
Storyblok MCP Server
A TypeScript Model Context Protocol server for the Storyblok Management API. It lets AI assistants and agents manage Storyblok content, workflows, and configuration safely and programmatically.
Why this project
Storyblok is powerful, but repetitive content operations and release workflows can be time-consuming. This server bridges MCP-compatible assistants with Storyblok so teams can:
Automate content ops (bulk updates, tagging, assets)
Orchestrate releases and workflows with less manual effort
Keep component libraries and schemas consistent
Give AI agents structured, typed access to Storyblok
Related MCP server: MCP Storyblok Server
Highlights
160 tools across 30 modules mapped to Storyblok Management API capabilities
Typed schemas with Zod for safer tool calls
MCP-first design for MCP-compatible clients
Simple config using environment variables
What it does in 15 seconds
Prompt
Find all stories updated in the last 7 days and tag them as "reviewed".Response (example)
Found 12 stories updated since 2025-12-28.
Applied tag "reviewed" to 12 stories.Quick Start
# Clone the repository
git clone https://github.com/hypescale/storyblok-mcp-server.git
cd storyblok-mcp-server
# Install dependencies
npm install
# Build
npm run buildCreate a .env file from the example and fill in your credentials:
cp .env.example .envThen start the server:
npm run startRequirements
Node.js >= 22
A Storyblok space and a personal access token for the Management API
Configuration
The server requires two environment variables (see .env.example):
STORYBLOK_SPACE_ID=your_space_id
STORYBLOK_MANAGEMENT_TOKEN=your_management_token
# Optional: set if your space is not hosted in the EU
STORYBLOK_REGION=euWhat they are used for:
Variable | Required | Description |
| yes | Your numeric Storyblok space ID |
| yes | Personal access token for the Management API |
| no | Server location of the space: |
| no | Override the API host entirely (e.g. a proxy); takes precedence over |
| no | Not used by any tool; accepted for backwards compatibility |
Requests that hit Storyblok's rate limit (HTTP 429; 3–6 req/s depending on plan) are retried automatically with exponential backoff, honoring Retry-After.
Tip: Use the smallest permission set possible for safety.
Usage with MCP Clients
This server is designed to work with any MCP-compatible client. Here are ready-to-copy configs for popular tools.
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"storyblok": {
"command": "node",
"args": ["/path/to/storyblok-mcp-server/dist/index.js"],
"env": {
"STORYBLOK_SPACE_ID": "your_space_id",
"STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
}
}
}
}Codex CLI / IDE
Codex supports MCP servers via CLI or by editing ~/.codex/config.toml. The CLI and IDE extension share the same config.
Option A: Configure with the Codex CLI
codex mcp add storyblok \
--env STORYBLOK_SPACE_ID=your_space_id \
--env STORYBLOK_MANAGEMENT_TOKEN=your_management_token \
--env STORYBLOK_DEFAULT_PUBLIC_TOKEN=your_public_token \
-- node /path/to/storyblok-mcp-server/dist/index.jsOption B: Configure with ~/.codex/config.toml
[mcp_servers.storyblok]
command = "node"
args = ["/path/to/storyblok-mcp-server/dist/index.js"]
[mcp_servers.storyblok.env]
STORYBLOK_SPACE_ID = "your_space_id"
STORYBLOK_MANAGEMENT_TOKEN = "your_management_token"
STORYBLOK_DEFAULT_PUBLIC_TOKEN = "your_public_token"Cursor
Create a project config at .cursor/mcp.json (or use the global config at ~/.cursor/mcp.json):
{
"mcpServers": {
"storyblok": {
"command": "node",
"args": ["/path/to/storyblok-mcp-server/dist/index.js"],
"env": {
"STORYBLOK_SPACE_ID": "your_space_id",
"STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
}
}
}
}Windsurf
Create ~/.codeium/mcp_config.json:
{
"mcpServers": {
"storyblok": {
"command": "node",
"args": ["/path/to/storyblok-mcp-server/dist/index.js"],
"env": {
"STORYBLOK_SPACE_ID": "your_space_id",
"STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
}
}
}
}VS Code
Create .vscode/mcp.json in your workspace:
{
"servers": {
"storyblok": {
"type": "stdio",
"command": "node",
"args": ["/path/to/storyblok-mcp-server/dist/index.js"],
"env": {
"STORYBLOK_SPACE_ID": "your_space_id",
"STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
}
}
}
}Continue
Create a YAML config at .continue/mcpServers/storyblok.yaml:
name: Storyblok MCP
version: 1.0.0
schema: v1
mcpServers:
- name: storyblok
command: node
args:
- /path/to/storyblok-mcp-server/dist/index.js
env:
STORYBLOK_SPACE_ID: your_space_id
STORYBLOK_MANAGEMENT_TOKEN: your_management_token
STORYBLOK_DEFAULT_PUBLIC_TOKEN: your_public_tokenCline
Open Cline settings and use "Configure MCP Servers" to open cline_mcp_settings.json, then add:
{
"mcpServers": {
"storyblok": {
"command": "node",
"args": ["/path/to/storyblok-mcp-server/dist/index.js"],
"env": {
"STORYBLOK_SPACE_ID": "your_space_id",
"STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
}
}
}
}Available Tools
The tool surface mirrors Storyblok's Management API. Total tool count and modules are defined in src/tools/index.ts.
Module | Tools | Description |
Stories | 18 | CRUD, bulk operations, publishing, versioning |
Components | 9 | Schema management, versioning, usage tracking |
Assets | 9 | Upload, organize, bulk operations |
Workflows | 6 | Workflow management and stages |
Releases | 5 | Release scheduling and deployment |
Datasources | 5 | Key-value data management |
Tags | 5 | Content tagging and organization |
Webhooks | 5 | Event notifications |
Collaborators | 4 | Team management |
Space Roles | 5 | Permissions and access control |
... | ... | And 20+ more modules |
Example Prompts
Use these prompts in your MCP client to see quick wins:
"List all stories updated in the last 7 days and tag them as 'reviewed'."
"Create a release for next Friday and add the homepage and pricing stories."
"Find unused components and tell me which stories still reference them."
"Upload these assets and organize them into a new 'Campaign' folder."
Development
# Run in development mode with hot reload
npm run dev
# Type check
npm run typecheck
# Run unit tests
npm test
# Build for production
npm run buildProject Structure
src/index.ts- MCP server entry pointsrc/tools/*- Tool modules mapped to Storyblok API areassrc/types/*- Shared API and Storyblok typessrc/tools/registry.ts- Module registration, tool counts and MCP tool annotationssrc/utils/*- HTTP helpers (retry, region, errors) and response formattingsrc/config.ts- Environment configuration and validation
Troubleshooting
ConfigError: STORYBLOK_* is missing- ensure.envis present and filled out.Run the
pingtool first: it verifies token, region and space ID in one call.401 Unauthorized- verifySTORYBLOK_MANAGEMENT_TOKEN.404 Not Found- double-checkSTORYBLOK_SPACE_ID, and thatSTORYBLOK_REGIONmatches where the space is hosted.
Tech Stack
TypeScript with strict type checking
@modelcontextprotocol/sdk for MCP implementation
Zod for runtime schema validation
Native fetch API for HTTP requests
Release and Versioning
When you're ready to cut a release:
Update
package.jsonversion (semantic versioning recommended).Update
README.mdif behavior or setup changed.Tag the release and publish a GitHub Release with notes.
This keeps the project easy to consume for open source users and downstream tools.
Security Notes
Never commit
.envfiles or tokens to git.Prefer tokens scoped to a dedicated Storyblok space for automation.
Rotate tokens if you suspect exposure.
Contributing
Issues and PRs are welcome. If you're planning a large change, open an issue first so we can align on scope and direction.
License
MIT
Built by hypescale | Maintained by Martin Kogut
Available Tools
160 toolsadd_collaboratorA
Adds a collaborator to a space in Storyblok. Use either role (string) OR space_role_id (int) OR space_role_ids (list).
Inputs: email (required), role, space_role_id, space_role_ids, +2 more.
add_webhookB
Adds a new webhook to a specified Storyblok space using the Management API.
Inputs: name (required), endpoint (required), actions (required), description, +2 more.
ai_translate_storyB
Translates a story's content into a specified language using AI.
Inputs: space_id (required), story_id (required), lang (required), code (required), +2 more.
backup_spaceB
Triggers a backup task for a Storyblok space using Management API.
Inputs: space_id (required).
bulk_create_storiesB
Creates multiple stories in Storyblok.
Inputs: stories (required).
bulk_delete_storiesB
Deletes multiple stories in Storyblok.
Inputs: story_ids (required).
bulk_move_assetsB
Move multiple assets to a specified folder.
Inputs: ids (required), asset_folder_id (required).
bulk_publish_storiesB
Publishes multiple stories by ID.
Inputs: story_ids (required).
bulk_restore_assetsB
Restores multiple previously deleted assets
Inputs: ids (required).
bulk_update_storiesB
Updates multiple stories in Storyblok, optionally publishing them.
Inputs: stories (required).
compare_story_versionsC
Compares two versions of a story to identify changes.
Inputs: story_id (required), version_v2 (required).
complete_asset_uploadC
Completes the asset upload process after S3 upload.
Inputs: asset_id (required).
create_access_tokenB
Create a new access token in the current Storyblok space via the Management API.
Inputs: access (required), name, branch_id, story_ids, +1 more.
create_approvalB
Creates an approval request for a story in a Storyblok space.
Inputs: story_id (required), approver_id (required).
create_asset_folderB
Create a new asset folder in the current Storyblok space.
Inputs: name (required), parent_id.
create_branchB
Creates a new branch (pipeline) in a Storyblok space via the Management API.
Inputs: name (required), source_id, url, position.
create_branch_deploymentB
Triggers a deployment of specified releases to a given branch (pipeline stage).
Inputs: branch_id (required), release_uuids (required).
create_commentB
Adds a comment to a discussion via the Storyblok Management API.
discussion_id: Numeric ID of the discussion.
message_json: Required array of message objects. Each must include "type", "text", and "attrs".
message: Optional plain-text field (can be null or string).
Inputs: discussion_id (required), message_json (required), message.
create_componentB
Creates a new component with all supported fields.
Inputs: name (required), display_name, schema, is_root, +8 more.
create_component_folderC
Creates a new component folder.
Inputs: name (required), parent_id.
create_datasourceC
Creates a new datasource in a specified Storyblok space.
Inputs: name (required), slug (required), dimensions.
create_datasource_entryB
Creates a new datasource entry in a specified Storyblok space.
Inputs: datasource_id (required), name (required), value (required).
create_discussionB
Creates a new discussion for a story via the Storyblok Management API.
Required:
story_id: ID of the story
title: Title of the discussion field
fieldname: Technical name of the discussion field
block_uid: ID of the discussion block
component: Component/block name this discussion belongs to
lang: Language code (e.g., "default", "en")
message_json: Array of message objects [{"type": "text", "text": "...", "attrs": {...}}, ...]
Inputs: story_id (required), title (required), fieldname (required), block_uid (required), +3 more.
create_extensionB
Creates a new extension in the specified context (organization or partner).
Inputs: name (required), slug (required), context (required), icon, +15 more.
create_field_pluginB
Creates a new field plugin (field type) in the specified context.
Args: name (str): Unique name for your plugin (e.g., 'my-geo-selector'). body (str): The uncompiled JavaScript source for the plugin. compiled_body (str): Required; empty string if developing locally. context (str): 'space', 'org', or 'partner'.
Inputs: name (required), body (required), compiled_body, context.
create_internal_tagC
Creates a new internal tag in a specified Storyblok space.
Inputs: name (required), object_type.
create_presetB
Creates a new preset in a Storyblok space via the Management API.
Inputs: name (required), component_id (required), preset (required), image, +3 more.
create_releaseB
Creates a new release in a specified Storyblok space.
Inputs: name (required), release_at, timezone, branches_to_deploy, +1 more.
create_release_approvalC
Creates a release approval for a given story and release.
Inputs: story_id (required), approver_id (required), release_id.
create_spaceC
Creates a new Storyblok space via the Management API.
Inputs: name (required), domain, story_published_hook, environments.
create_space_roleB
Creates a new custom space role with specific permissions.
Inputs: role_name (required), permissions (required), allowed_paths, field_permissions, +7 more.
create_storyC
Creates a new Storyblok story. Supports all documented fields including publishing.
Inputs: name (required), slug (required), content (required), parent_id, +12 more.
create_story_scheduleC
Creates a new story schedule via the Storyblok Management API.
Inputs: story_id (required), publish_at (required), language.
create_tagB
Creates a new tag in a Storyblok space via the Management API.
Inputs: name (required), story_id.
create_taskC
Creates a new task in a specified Storyblok space using the Management API.
Inputs: name (required), task_type, webhook_url, description, +2 more.
create_workflowB
Creates a new workflow in a Storyblok space via the Management API.
Inputs: name (required), content_types (required).
create_workflow_stageB
Creates a new workflow stage in a Storyblok space via the Management API.
Inputs: name (required), color (required), is_default, user_ids, +11 more.
create_workflow_stage_changeB
Creates a new workflow stage change for a story in a Storyblok space via the Management API.
Inputs: story_id (required), workflow_stage_id (required).
debug_story_accessC
Debug access to a specific story via various fetch parameters.
Inputs: story_id (required).
delete_access_tokenB
Delete an access token from the current Storyblok space using the Management API.
Inputs: token_id (required).
delete_approvalB
Deletes an approval from a specified Storyblok space.
Inputs: approval_id (required).
delete_assetC
Deletes an asset from Storyblok.
Inputs: id (required).
delete_asset_folderB
Delete an asset folder from the current Storyblok space.
Inputs: folder_id (required).
delete_branchB
Deletes a branch (pipeline) by its ID in a Storyblok space.
Inputs: branch_id (required).
delete_collaboratorB
Deletes a collaborator from a specified Storyblok space. Can delete by collaborator_id or sso_id.
Inputs: collaborator_id (required), sso_id.
delete_commentC
Deletes a comment from a discussion via the Storyblok Management API.
discussion_id: Numeric ID of the discussion.
comment_id: Numeric ID of the comment.
Inputs: discussion_id (required), comment_id (required).
delete_componentB
Deletes a component by ID.
Inputs: id (required).
delete_component_folderA
Deletes a component folder (component group) by its ID.
Inputs: folder_id (required).
delete_datasourceB
Deletes a datasource from a specified Storyblok space.
Inputs: datasource_id (required).
delete_datasource_entryB
Deletes a datasource entry from a specified Storyblok space using the Management API.
Inputs: datasource_entry_id (required).
delete_extensionA
Deletes an existing extension in the specified context (organization or partner).
Inputs: extension_id (required), context.
delete_field_pluginA
Deletes a field plugin by its ID.
Args: field_type_id (int): Numeric ID of the field plugin to delete.
Inputs: field_type_id (required).
delete_internal_tagB
Deletes an internal tag (asset/component) in a specified Storyblok space.
Inputs: internal_tag_id (required).
delete_multiple_assetsB
Deletes multiple assets by numeric IDs using the Storyblok Management API.
Inputs: ids (required).
delete_presetB
Deletes a preset from a Storyblok space using the Management API.
Inputs: preset_id (required).
delete_releaseD
Deletes a release.
Inputs: release_id (required).
delete_spaceA
Permanently deletes a Storyblok space using the Management API.
Inputs: space_id (required).
delete_space_roleB
Deletes a space role using the Storyblok Management API.
Inputs: space_role_id (required).
delete_storyB
Deletes a story by ID.
Inputs: id (required).
delete_story_scheduleB
Deletes a story schedule entry via the Storyblok Management API.
Inputs: story_scheduling_id (required).
delete_tagC
Deletes a tag from Storyblok.
Inputs: id (required).
delete_taskA
Deletes an existing task in a specified Storyblok space using the Management API.
Inputs: task_id (required).
delete_webhookA
Deletes an existing webhook endpoint in a specified Storyblok space.
Inputs: webhook_endpoint_id (required).
delete_workflowA
Deletes a workflow by its ID in a Storyblok space via the Management API. The default workflow cannot be deleted.
Inputs: workflow_id (required).
delete_workflow_stageB
Deletes a workflow stage in a Storyblok space via the Management API.
Inputs: workflow_id (required).
duplicate_spaceB
Duplicates an existing Storyblok space via the Management API.
Inputs: original_space_id (required), new_space_name (required), domain, story_published_hook, +3 more.
duplicate_workflowB
Duplicates an existing workflow in a Storyblok space via the Management API.
Inputs: workflow_id (required), name (required), content_types (required).
fetch_asset_folderA
Fetch details of a specific asset folder by its ID.
Inputs: folder_id (required).
fetch_assetsC
Retrieve multiple assets from Storyblok Management API.
Inputs: page, per_page, search, folder_id, +6 more.
fetch_component_foldersA
Retrieves all component folders (non-paginated), with optional filtering.
Inputs: search, with_parent.
fetch_componentsC
Fetches components with server-side filters, sorting, and option to include groups.
Inputs: component_summary, include_schema_details, filter_by_name, is_root, +3 more.
fetch_space_rolesC
Retrieves multiple space roles for a given space.
Inputs: search, by_ids.
fetch_spacesB
Retrieve all accessible spaces.
Inputs: no named parameters.
fetch_storiesA
Fetch multiple stories from Storyblok with advanced filtering and pagination.
Inputs: page, per_page, contain_component, text_search, +26 more.
get_assetA
Gets a specific asset by ID.
Inputs: id (required).
get_componentB
Gets a specific component by ID.
Inputs: id (required).
get_component_usageB
Finds stories where a component is used in content (draft & published).
Inputs: component_name (required).
get_spaceB
Fetch a specific space by ID.
Inputs: space_id (required).
get_space_roleA
Retrieve a single space role by ID via the Storyblok Management API.
Inputs: space_role_id (required).
get_storyA
Retrieves a specific story by its ID.
Inputs: story_id (required).
get_story_versionsC
Retrieves versions (revisions) of stories.
Inputs: by_story_id (required), version_id, by_release_id, page, +2 more.
get_unpublished_dependenciesB
Retrieves unpublished dependencies for one or more stories.
Inputs: story_ids (required), release_id.
init_asset_uploadB
Initializes asset upload and returns signed S3 upload URL.
Inputs: filename (required), size (required), content_type (required).
list_toolsA
Lists all available tool categories with their tool counts. Returns module-level summary of 130 Storyblok Management API tools.
Inputs: no named parameters.
pingA
Checks server health and Storyblok API connectivity.
Inputs: no named parameters.
publish_storyB
Publishes a Storyblok story by its ID.
Inputs: story_id (required), lang, release_id.
resolve_discussionB
Marks a discussion as resolved via the Storyblok Management API.
discussion_id: Numeric ID of the discussion.
solved_at: Timestamp when the discussion is resolved (ISO 8601 format).
Inputs: discussion_id (required), solved_at (required).
restore_component_versionC
Restores a component to a previous version.
Inputs: version_id (required), component_id (required).
restore_storyB
Restores a story to a specific version.
Inputs: id (required), version_id (required).
retrieve_all_extensionsA
Retrieves all extensions (plugins) from the specified context.
Args: context (str): The context to retrieve extensions from. Options are 'org' for organization-level or 'partner' for partner-level extensions.
Inputs: context (required).
retrieve_all_extension_settingsB
Retrieve settings for all extensions installed in a space.
Inputs: space_id (required).
retrieve_asset_foldersB
Retrieve a list of asset folders from the current Storyblok space.
Inputs: search, with_parent, by_ids, by_uuids.
retrieve_component_versionsA
Retrieves paginated versions of a component.
Inputs: component_id (required), page, per_page.
retrieve_extensionC
Retrieves the settings of a specific extension by its numeric ID.
Args: extension_id (int): The numeric ID of the extension. context (str): The context to retrieve the extension from. Options are 'org' for organization-level or 'partner' for partner-level extensions.
Inputs: extension_id (required), context (required).
retrieve_extension_settingsB
Retrieve settings for a specific extension in a space.
Inputs: space_id (required), extension_id (required).
retrieve_field_pluginA
Retrieves a single field plugin by its ID in the specified context.
Args: field_type_id (int): Numeric ID of the field plugin. context (str): 'space', 'org', or 'partner'.
Inputs: field_type_id (required), context.
retrieve_field_pluginsA
Retrieves multiple field plugins (field types) across different contexts.
Args: context (str): 'space', 'org', or 'partner' only_mine (int): 1 = only plugins created by authenticated user page (int): pagination page number per_page (int): plugins per page (max 100) search (str): search filter for plugin name or slug
Inputs: context, only_mine, page, per_page, +1 more.
retrieve_idea_discussions_commentsC
Retrieves comments for a specific idea discussion in a Storyblok space.
discussion_uuid: UUID of the discussion in the idea.
Inputs: discussion_uuid (required).
retrieve_multiple_access_tokensA
Retrieve all access tokens for the current Storyblok space using the Management API.
Inputs: no named parameters.
retrieve_multiple_activitiesC
Retrieves activity logs for a specified Storyblok space.
Inputs: created_at_gte, created_at_lte, by_owner_ids, types.
retrieve_multiple_approvalsC
Retrieves multiple approvals from a specified Storyblok space.
Inputs: approver (required), page, per_page.
retrieve_multiple_branchesB
Retrieves multiple branches (pipelines) in a Storyblok space via the Management API.
Inputs: by_ids, search.
retrieve_multiple_collaboratorsA
Retrieves a paginated list of collaborators (users) in a specified Storyblok space.
Inputs: page, per_page.
retrieve_multiple_commentsB
Retrieves all comments from a specific discussion via the Storyblok Management API.
discussion_id: Numeric ID of the discussion.
Inputs: discussion_id (required).
retrieve_multiple_datasource_entriesA
Retrieves multiple datasource entries from a specified Storyblok space. Requires datasource_id or datasource_slug.
Inputs: datasource_id, datasource_slug, dimension.
retrieve_multiple_datasourcesB
Retrieves multiple datasources from a specified Storyblok space.
Inputs: search, by_ids.
retrieve_multiple_discussionsA
Retrieves multiple discussions for a specific story in a Storyblok space.
story_id: Numeric ID of the story.
per_page: Number of discussions per page (default: 25, max: 100).
page: Page number to retrieve (default: 1).
by_status: Filter discussions by status (e.g., 'unsolved', 'solved').
Inputs: story_id (required), per_page, page, by_status.
retrieve_multiple_internal_tagsB
Retrieves internal tags (asset/component) from a specified Storyblok space. Use by_object_type 'asset' or 'component' to filter.
Inputs: by_object_type, search.
retrieve_multiple_presetsB
Retrieves multiple presets from a Storyblok space using the Management API.
Inputs: component_id.
retrieve_multiple_releasesB
Retrieves multiple releases from a specified Storyblok space.
Inputs: space_id (required), branch_id.
retrieve_multiple_story_schedulesA
Retrieves multiple story scheduling entries in a Storyblok space via the Management API.
Inputs: space_id (required), by_status.
retrieve_multiple_tagsC
Retrieves multiple tags from a specified Storyblok space using the Management API.
Inputs: search.
retrieve_multiple_tasksC
Retrieves multiple tasks from a specified Storyblok space using the Management API.
Inputs: space_id (required), page, per_page.
retrieve_multiple_webhooksB
Retrieves multiple webhook endpoints from a specified Storyblok space using the Management API.
Inputs: page, per_page.
retrieve_multiple_workflowsA
Retrieves all workflows in a Storyblok space via the Management API. Optionally filter by content type (e.g., 'page', 'article', etc.)
Inputs: content_type.
retrieve_multiple_workflow_stage_changesC
Retrieves multiple workflow stage changes in a Storyblok space via the Management API.
Inputs: space_id (required), with_story.
retrieve_multiple_workflow_stagesB
Retrieves multiple workflow stages in a Storyblok space via the Management API.
Inputs: exclude_id, by_ids, search, in_workflow.
retrieve_my_discussionsB
Retrieves discussions you're involved in within a Storyblok space.
page: Page number (default 1).
per_page: Items per page (default 25, max 100).
by_status: Filter discussions by status ('unsolved' or 'solved').
Inputs: page, per_page, by_status.
retrieve_one_story_scheduleA
Retrieves a single story schedule entry by its ID in a Storyblok space via the Management API.
Inputs: story_scheduling_id (required).
retrieve_single_activityB
Retrieves a single activity log by its ID from a specified Storyblok space.
Inputs: activity_id (required).
retrieve_single_approvalA
Retrieves a single approval by its ID from a specified Storyblok space.
Inputs: approval_id (required).
retrieve_single_branchB
Retrieves a single branch (pipeline) by its ID via the Storyblok Management API.
Inputs: branch_id (required).
retrieve_single_component_folderB
Retrieves a single component folder (component group) by its ID.
Inputs: folder_id (required).
retrieve_single_component_versionA
Retrieves the schema details of a specific component version.
Inputs: component_id (required), version_id (required).
retrieve_single_datasourceA
Retrieves a single datasource from a specified Storyblok space.
Inputs: datasource_id (required).
retrieve_single_datasource_entryB
Retrieves a single datasource entry via the Storyblok Management API.
Inputs: datasource_entry_id (required).
retrieve_single_presetB
Retrieves a single preset from a Storyblok space using the Management API.
Inputs: preset_id (required).
retrieve_single_releaseB
Retrieves a single release from a specified Storyblok space.
Inputs: release_id (required).
retrieve_single_taskA
Retrieves a single task from a specified Storyblok space using the Management API.
Inputs: task_id (required).
retrieve_single_webhookB
Retrieves a single webhook from a specified Storyblok space using the Management API.
Inputs: webhook_endpoint_id (required).
retrieve_single_workflowB
Retrieves a single workflow by its ID in a Storyblok space via the Management API.
Inputs: workflow_id (required).
retrieve_single_workflow_stageA
Retrieves a single workflow stage by its ID in a Storyblok space via the Management API.
Inputs: workflow_stage_id (required).
retrieve_specific_discussionB
Retrieves a specific discussion by its ID in a Storyblok space.
discussion_id: Numeric ID of the discussion.
Inputs: discussion_id (required).
tag_bulk_associationC
Adds tags to multiple stories in a Storyblok space.
Inputs: stories (required).
unpublish_storyB
Unpublishes a Storyblok story by its ID.
Inputs: story_id (required), lang.
update_access_tokenB
Update an existing access token in the current Storyblok space via the Management API.
Inputs: token_id (required), access, name, branch_id, +2 more.
update_assetC
Update an existing asset's metadata or settings.
Inputs: asset_id (required), asset_folder_id, internal_tag_ids, locked, +9 more.
update_asset_folderB
Update an existing asset folder's name or parent in the current Storyblok space.
Inputs: folder_id (required), name, parent_id.
update_branchA
Updates an existing branch (pipeline) in a Storyblok space via the Management API.
Inputs: branch_id (required), name, source_id, url, +1 more.
update_collaboratorB
Updates roles, permissions, or access paths for an existing collaborator.
Inputs: collaborator_id (required), role, user_id, permissions, +4 more.
update_commentA
Updates a comment in a discussion via the Storyblok Management API.
Required:
discussion_id: Numeric ID of the discussion.
comment_id: Numeric ID of the comment.
Payload:
message_json: Required. Array of message objects, each with keys "type", "text", "attrs".
message: Optional string or null.
Inputs: discussion_id (required), comment_id (required), message_json (required), message.
update_componentC
Updates an existing component with all supported fields.
Inputs: id (required), name, display_name, schema, +10 more.
update_component_folderC
Updates an existing component folder (component group).
Inputs: folder_id (required), name, parent_id, space_id.
update_datasourceC
Updates an existing datasource in a specified Storyblok space.
Inputs: datasource_id (required), name, slug, dimensions.
update_datasource_entryB
Updates an existing datasource entry in a specified Storyblok space.
Inputs: datasource_entry_id (required), name, value, dimension_value, +1 more.
update_extensionB
Updates an existing extension in the specified context (organization or partner).
Inputs: extension_id (required), context, name, slug, +16 more.
update_field_pluginC
Updates an existing field plugin in the specified context.
Args: field_type_id: Numeric ID of the field plugin. body: Updated uncompiled JS source. compiled_body: Updated compiled JS source. name: Optional new name (must still be unique). options: Optional config options for the plugin. space_ids: Optional space assignment list. context: 'space', 'org', or 'partner'.
Inputs: field_type_id (required), body, compiled_body, name, +3 more.
update_internal_tagB
Updates an internal tag (asset/component) in a specified Storyblok space.
Inputs: internal_tag_id (required), name, object_type.
update_presetC
Updates an existing preset in a Storyblok space via the Management API.
Inputs: preset_id (required), name, component_id, preset, +4 more.
update_releaseB
Updates an existing release in a specified Storyblok space.
Inputs: release_id (required), name, release_at, timezone, +3 more.
update_spaceB
Updates an existing Storyblok space via the Management API.
Inputs: space_id (required), name, domain, uniq_domain, +12 more.
update_space_roleB
Updates a space role's configuration via the Storyblok Management API.
Inputs: space_role_id (required), role_name, permissions, allowed_paths, +8 more.
update_storyB
Updates an existing Storyblok story by ID. Supports all documented fields including publishing.
Inputs: story_id (required), name, slug, content, +18 more.
update_story_scheduleB
Updates an existing story schedule via the Storyblok Management API.
Inputs: space_id (required), story_scheduling_id (required), publish_at, language.
update_tagA
Updates the name of an existing tag in a Storyblok space.
Inputs: tag_id (required), new_name (required).
update_taskC
Updates an existing task in a specified Storyblok space using the Management API.
Inputs: task_id (required), name, description, task_type, +3 more.
update_webhookC
Updates an existing webhook endpoint in a specified Storyblok space.
Inputs: webhook_endpoint_id (required), name, endpoint, actions, +3 more.
update_workflowB
Updates an existing workflow in a Storyblok space via the Management API.
Inputs: workflow_id (required), name (required), content_types (required).
update_workflow_stageB
Updates an existing workflow stage in a Storyblok space via the Management API.
Inputs: workflow_id (required), name (required), color (required), is_default, +11 more.
validate_story_contentA
Validates a story's content against a component schema. Either provide story_id (to fetch) or story_content directly.
Inputs: component_name (required), story_id, story_content, space_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
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.
Maintenance
Related MCP Connectors
The official MCP Server from Mia-Platform to interact with Mia-Platform Console
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Hosted Kontent.ai MCP server to manage content, types, taxonomies, and workflows
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server for interacting with Contentstack's Content Management API1511 npm2TypeScriptMIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive server enabling natural language interaction with Storyblok CMS for managing stories, assets, components, releases, and other content through a modular architecture.1ISC
- AlicenseCqualityDmaintenanceThe Storyblok MCP server enables your AI assistants to directly access and manage your Storyblok spaces, stories, components, assets, workflows, and more.41PythonMIT
- 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.7460 npm-