Enables comprehensive interaction with the Storyblok Management API to manage stories, tags, components, assets, releases, workflows, webhooks, and datasources.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Storyblok MCPList the 5 most recent stories from my space"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Storyblok MCP
MCP server for Storyblok: fetch stories, manage tags, and use AI (Cursor, Claude Desktop) to work with your content. You only need to set 2–3 env variables.
What you need
Node.js 18+ — nodejs.org (LTS)
Storyblok Space ID — Space settings or from the app URL:
app.storyblok.com/#/me/spaces/<ID>/Management API token — Storyblok → Settings → Access tokens → Create (full access or at least Stories + Tags)
Quick start
1. The Universal Way (Best for non-technical users)
Deploy this server to Vercel. Once live, anyone can connect to their own Storyblok space using just the URL and token.
Advanced Cloud Options (SSE)
You can further customize the connection using headers or URL parameters:
Specific Space ID: Use the URL
.../sse/12345or set thex-space-idheader.Custom API Proxy: Set the
x-api-baseheader to point to your own Storyblok MAPI proxy.Private Access Key: If the server has an
MCP_API_KEYset, provide it via thex-mcp-keyheader.
Example with all options:
2. Local Development
Edit .env and set at least:
3. Running with Docker
You can also run the server using Docker. This is great for consistent deployments.
The Docker image defaults to SSE mode on port 3000.
Deploying to Kubernetes
Push to Registry:
docker tag storyblok-mcp your-registry/storyblok-mcp:latest docker push your-registry/storyblok-mcp:latestApply Manifests: Use the provided k8s-deployment.yaml as a template. It sets up a Deployment, a Service, and an Ingress for custom domain support (HTTPS).
External URL: Once deployed, you can point your domain (e.g.,
mcp.yourdomain.com) to your Ingress controller's IP.
4. Connect to Cursor or Claude Desktop
Cursor — edit MCP config (e.g. ~/Library/Application Support/Cursor/User/globalStorage/cursor.mcp/mcp.json or Settings → MCP):
Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
Replace the path with your actual storyblok-mcp folder path. Restart Cursor or Claude.
start-with-env.js loads .env from the project folder, so you don’t need to put secrets in the MCP config.
Env variables
Variable | Required | Description |
| ✅ | Your Storyblok space ID |
| ✅ | Management API token |
| ❌ |
|
| ❌ | Override API base (if proxying) |
Region (EU, US, etc.)
If your Storyblok Space is in the US or another region, set:
Options: eu, us, ca, ap, cn. Default: eu.
Custom API URL
Only if you proxy the Storyblok Management API through your own domain:
SSE Custom Proxy
In SSE mode, you can also specify the proxy per-connection:
The proxy must forward to the real Storyblok MAPI. Otherwise leave this unset.
Tools
Full-featured TypeScript implementation for the Storyblok Management API.
Category | Tools |
Stories |
|
Tags |
|
Components |
|
Assets |
|
Releases |
|
Workflows |
|
Webhooks |
|
Datasources |
|
Space |
|
Meta |
|
Ping |
|
Example prompts
“Fetch my Storyblok stories”
“List all tags in my space”
“Suggest a tag for each of my blog posts and add them”
“Add the tag ‘product-launch’ to story ID …”
Troubleshooting
“Missing env” —
.envmust be next tostart-with-env.jsand containSTORYBLOK_SPACE_IDandSTORYBLOK_MANAGEMENT_TOKEN.401 from Storyblok — Token invalid or expired; create a new Management token with Stories + Tags.
MCP not listed — Use the absolute path to
start-with-env.jsand restart Cursor/Claude.“Cannot find module” — Run
npm installandnpm run buildin yourstoryblok-mcpfolder.
Reference
This server cannot be installed