Storyblok MCP. Manage content structure and assets via conversation.
Storyblok MCP lets your AI client manage content structure and assets directly within Storyblok. It gives you programmatic control over headless CMS environments. You can list entire content spaces, analyze available component blueprints, draft new stories, update existing articles, and find all media files without ever touching the visual editor.
Give Claude and any AI agent real-world access
Lists all accessible Storyblok environments so your agent knows where to start working.
Retrieves lists of existing articles or scans the entire media library for multimedia files.
Lists all defined content components, helping you understand what structural elements are available to build with.
Creates new articles or updates fields in existing stories using structured data inputs.
Checks who has editing access to a specific content space, helping manage internal permissions.
Ask an AI about this
Waiting for input…
What AI agents can do with Storyblok: 9 Content Management Tools
Use these tools to programmatically list, create, modify, and analyze every structural element within your Storyblok content space.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Storyblok MCPCreate Content Story
Builds a brand new content article by providing its name, slug, and structured JSON data.
Delete Content Story
Permanently removes an existing story from the content repository. This action can't...
Get Story Details
Fetches all specific details for a single, identified content article.
List Assets
Scans and retrieves a list of every media file stored within the Storyblok space.
List Components
Shows all structural blueprints that can be used to build content pages.
List Spaces
Lists every distinct and accessible Storyblok environment or 'space'.
List Stories
Retrieves a list of article titles and metadata within a specific content space.
List Space Users
Lists all users who have been granted access permissions for the targeted space.
Update Content Story
Modifies specific fields of an article that already exists in the system.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Storyblok, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Storyblok. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The headache of manual CMS management
Today, managing content means jumping between the visual editor and a separate data panel. You have to copy component IDs here, paste metadata names there, and cross-reference asset URLs in a spreadsheet just to create one page draft.
With this MCP, you simply tell your agent, 'Build me an article about X.' Your AI client handles all the underlying steps—it finds the right blueprints, validates the structure, and writes the payload. You get content that's ready for publication, not a half-finished mess requiring manual cleanup.
Crafting Content with Storyblok MCP
The repetitive, frustrating tasks of listing every asset via `list_assets` or manually checking which components are available using `list_components` disappear. Your agent handles the discovery and validation steps automatically.
What changes is that content becomes a data resource you can manipulate with plain language instructions. You stop clicking; you start commanding.
What Storyblok MCP does for your AI
Managing complex digital content used to mean clicking through endless dashboards or copy-pasting structural IDs from one tab to another. This MCP changes that. It connects your AI agent directly into Storyblok's backend, treating your entire content repository like a database you can talk to. You instruct your agent what you need—say, 'Give me all the components used in our marketing space and draft a new story using those elements.' The system finds the necessary blueprints, validates them against existing data, and then builds or updates the content for you.
It’s about treating content not as visual blocks, but as structured data. If you're building out a complex site structure and need an AI assistant that understands component hierarchies and asset libraries, Vinkius has this MCP ready to go.
019d760d-9bca-70b9-8b9b-59bcf6ebadf5 How to set up Storyblok MCP
The bottom line is that you tell your AI client what content structure you want, and this MCP executes the necessary steps inside Storyblok to make it happen.
Establish the Storyblok MCP module on your preferred AI client.
Provide an authorized connection token in the MCP settings so your agent can execute commands securely.
Prompt your agent with a specific request, like asking it to retrieve component blueprints and then draft a new story structured as JSON.
Who uses Storyblok MCP
This connector is for content architects, frontend developers, and SEO managers who struggle with manually validating component schemas or updating complex content structures. If your job involves transforming design ideas into production-ready CMS data, you need this.
Uses the MCP to analyze available components and systematically draft new stories, ensuring metadata parameters are correct before handover.
Queries component structural IDs or retrieves nested object data programmatically to isolate dependencies for front-end coding.
Runs checks on existing story structures and bulk updates textual assets across multiple active drafts efficiently.
Benefits of connecting Storyblok MCP
You can generate a new story or update an existing one using create_content_story or update_content_story, feeding the agent structured JSON payloads instead of typing out markdown manually.
When you need to know what structural parts are available, running list_components shows you all schema blueprints. This stops guesswork and standardizes development across teams.
To prepare a new campaign page, your agent can first use list_assets to find every relevant image or video, making sure the content is sourced before writing begins.
Need an overview of what's published? Running list_stories gives you titles and metadata for all articles in a space, letting you build a comprehensive index instantly.
Before touching content, use list_space_users to audit who has access rights. This is critical for maintaining security and controlling modifications across different projects.
Storyblok MCP use cases
Launching an Article Draft
A Content Architect needs to publish a new thought leadership piece. They ask their agent to draft it, which uses list_components first, then calls create_content_story, ensuring the article adheres to the correct format and includes proper metadata.
Updating Product Information
A Marketing Manager updates pricing across fifty product pages. Instead of logging into each one, they instruct their agent to run list_stories for all relevant spaces and then use update_content_story in bulk.
Building a Component Library
A developer wants to know if the team has already built a 'Testimonial Block.' They ask the agent, which uses list_components, confirming the exact structural ID needed for their front-end code.
Media Audit for Compliance
An SEO manager suspects outdated imagery. They tell their agent to run list_assets across all spaces, giving them a complete inventory of every media file that needs review or replacement.
Storyblok MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to edit content without context
Manually trying to update an article by guessing the correct JSON structure, resulting in errors because you don't know if a field is mandatory or deprecated.
First, run list_components to see the official blueprints. Then use that knowledge when calling update_content_story to ensure your data payload matches Storyblok's required schema.
Accidentally deleting core content
Running a mass delete command based on an assumption, which permanently removes critical stories or assets without confirmation.
Always run list_stories first to verify the scope of what you're dealing with. If deletion is necessary, use delete_content_story only after confirming all necessary data has been backed up.
Forgetting which space to target
Running a content update that targets the wrong client environment (Space A instead of Space B), causing massive deployment errors.
Always start by calling list_spaces to get an authoritative list of all environments. Then, specify the exact Space ID when using any creation or retrieval tool.
When to use Storyblok MCP
Use this MCP if your job requires manipulating content data in a structured way—if you are dealing with component blueprints, asset libraries, or large batches of articles. It excels at programmatic schema generation and validation. Don't use it if all you need is simple drafting or basic text generation; for that, a generic LLM agent will suffice. However, if your goal is to publish the content into Storyblok's system, this is mandatory. If you are only interested in user permissions, rely on list_space_users instead of trying to guess which API calls might work.
Frequently asked questions about Storyblok MCP
How do I find out which Storyblok spaces are available using the Storyblok MCP? +
You run list_spaces. This tool gives your agent a list of all accessible environments, letting you target the right project before any work begins.
Can I use the Storyblok MCP to check if an article exists? +
Yes. You can first run list_stories within a specific space ID. This gives you a list of existing titles, confirming if your desired content piece is already published.
How does the Storyblok MCP help with structured data creation? +
You use create_content_story. You just provide the name and the JSON payload, and it handles building the article according to your specified schema.
What if I need to modify an existing blog post using Storyblok MCP? +
Use update_content_story. This requires you to provide both the space ID and the story ID, plus the specific fields you want to change in the article.
Does the Storyblok MCP let me see what media is available? +
Yes. The list_assets tool scans your entire media library and gives you a full list of all images, videos, and other files ready for integration into your content.