home / mcp / storyblok mcp server
A modular, extensible MCP Server for managing Storyblok spaces, stories, components, assets, workflows, and more via the Model Context Protocol (MCP).
Configuration
View docs{
"mcpServers": {
"kiran1689-storyblok-mcp-server": {
"command": "uv",
"args": [
"run",
"--with",
"mcp",
"mcp",
"run",
"C:\\path\\to\\storyblok-mcp-server\\server.py"
],
"env": {
"STORYBLOK_SPACE_ID": "your_space_id",
"STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
}
}
}
}The Storyblok MCP Server lets your AI assistants directly access and manage your Storyblok spaces, stories, components, assets, workflows, and more. It enables you to perform create, read, update, and delete operations across Storyblok resources through a programmable MCP interface, making it easier to automate content workflows and integrations.
You connect your MCP client to the Storyblok MCP Server by running the local server process and exposing a control endpoint that your client can talk to. Once connected, you can perform CRUD operations across stories, components, assets, tags, releases, workflows, and many other Storyblok resources. The server exposes a wide range of tools you can call from your MCP client, including bulk operations and meta-tool discovery to see what’s available at runtime.
Prerequisites: you need Python and a runtime tool for MCP clients. You also need network access to install Python dependencies and run the local MCP server.
1. Clone or obtain the MCP server package and navigate to its directory.
2. Install the Python dependencies listed for the server.
3. Create a local configuration file with your Storyblok credentials and space ID.
4. Run the local MCP server using the provided runtime command.
Configuration uses environment variables to securely provide your Storyblok credentials and space information. You can run the server locally and connect with an MCP client to start issuing commands against your Storyblok resources. The server supports a broad set of resources and tools, including assets, components, stories, data sources, pipelines, webhooks, and workflows. When using a client, you may enable meta-tool discovery to list all available tools at runtime.
Security considerations: keep tokens and space IDs in secure environment variables and avoid committing them to version control. If you are exposing the server over a network, ensure you use proper authentication and restricted access.
Manage access tokens for Storyblok API with retrieve, create, update, and delete operations.
Retrieve or list activity logs related to Storyblok activity within the space.
Handle approval workflows, including listing, creating, updating, and deleting approvals.
Manage assets: upload, update, delete, and list assets.
Manage folders that organize assets.
Manage deployments for different branches of content.
Manage collaborators in a Storyblok space, including adding or removing members.
CRUD operations for Storyblok components, including usage and versioning.
Manage folders for organizing components.
Manage entries within data sources.
Manage data sources, including CRUD and entries.
Manage discussions and comments within the space.
Manage Storyblok extensions (create, update, delete, and retrieve).
Manage custom field plugins for components.
Manage internal tags used for assets and stories.
Meta tool to discover all available tools at runtime.
Health check and server status endpoint.
Manage pipelines for content delivery, including branches.
Manage field presets for components.
Manage releases, including create, update, and publish.
Schedule stories for publishing.
Manage space settings and information.
Manage roles and permissions within a space.
CRUD operations for stories, with bulk and validation options.
Manage tags with CRUD operations and bulk association.
Manage tasks including CRUD and webhooks.
Manage webhooks (CRUD and triggering).
Manage workflows and stages.
Manage individual workflow stages.
Track changes within workflow stages.