Storyblok MCP Server
Connect Storyblok to your AI agents with the Storyblok MCP server.
Updated
What is Storyblok MCP?
The Storyblok MCP server is a Model Context Protocol server that connects Storyblok to AI agents and assistants as a set of tools. With it connected, an agent can work with Storyblok (headless cms — stories, components, spaces, assets, content blocks) directly — instead of you copying data in and out by hand.
It is a remote MCP server that uses a bearer token, so you point your client at the server URL, authorize once, and the Storyblok tools become available to the model.
Connect the Storyblok MCP server
Connect Storyblok MCP to Claude Code
- 1
Add the server
Use `claude mcp add` with the Storyblok MCP server URL (or its `npx` command), following the official docs.
- 2
Authorize
Complete authentication (a bearer token) so Claude Code can call the server.
- 3
Verify
Ask Claude to use a Storyblok tool to confirm the connection is live.
Connect Storyblok MCP to Cursor
- 1
Open MCP settings
In Cursor, go to Settings → MCP → Add new server.
- 2
Add Storyblok
Provide the Storyblok MCP server URL or command and complete authentication.
- 3
Test
Reference Storyblok from chat to confirm Cursor can reach the tools.
Sample use cases
An agent monitors content entries nearing their scheduled publish date and sends a reminder to the assigned editor
Fewer missed deadlines and more consistent publishing cadence.
A scheduled agent pulls all draft stories older than 30 days and posts a stale-content report to Slack
Reduced content debt and clearer editorial backlog visibility.
An agent automatically translates new stories into target languages using the Storyblok content tree
Faster localization turnaround without manual copy-paste between language versions.
A content agent creates new landing pages from a template, filling in SEO metadata and hero images based on a brief
Marketing can launch campaign pages in minutes instead of hours.
An agent validates all published stories for broken internal links and missing alt text
Improved site health scores and accessibility compliance.
A nightly agent syncs product data from an e-commerce platform into Storyblok product stories
Product pages always reflect the latest pricing and availability.
An agent archives stories that have been unpublished for more than 90 days and logs the action
Cleaner content repository with an auditable cleanup trail.
Using Storyblok MCP with Gamut
On Gamut, the Storyblok MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Storyblok and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.
Frequently asked questions
What content operations can the Storyblok MCP server automate?
The server exposes tools for creating, reading, updating, and publishing stories, managing assets, and working with Storyblok's component-based content model. Agents can draft pages, schedule publishes, and run bulk content audits.
Does the Storyblok MCP server support multi-language content?
Yes. Agents can read and write field-level translations within Storyblok's internationalization framework, making it possible to automate localization workflows across all configured languages.
Can an agent manage Storyblok assets through MCP?
Yes. The server provides tools to upload, tag, and organize assets in the Storyblok asset library, enabling automated image optimization and media management pipelines.
Is the Storyblok MCP server compatible with headless site builds?
Absolutely. Since Storyblok is headless by design, MCP-driven content changes integrate seamlessly with static site generators and front-end frameworks that pull content via the Storyblok API.