Storyblok MCP Server

Your agent connects directly to a headless CMS, giving you hands-on control over content—no need for the visual editor, trust me. You can programmatically manage entire content spaces and structure complex data stories using just conversation. This lets your AI client interact with Storyblok's backbone, bypassing the traditional click-and-drag workflow entirely.

It’s all about controlling the data flow directly from your chat interface.

Discovering Content Structure and Spaces

You can start by getting a full list of every accessible content space using list_spaces, so you know exactly what environments you're playing with. If you need an overview of existing articles, use list_stories to fetch all content titles within a specific space ID.

Managing Stories: Create, Read, Update, Delete (CRUD)

The server gives you full lifecycle control over stories. To build something brand new, invoke create_content_story: you just provide the story's name, its unique slug, and a detailed content JSON payload, and it builds the article for you. If that story needs tweaking later, use update_content_story; you gotta supply both the space ID and the existing story ID to modify any of its fields.

For quick reference on an existing piece, run get_story_details with a specific story's ID to grab every detail about it. You can also manage the whole collection by running list_stories again.

When you’re done with content, and you know for sure you never want it back, delete_content_story permanently removes an existing Storyblok story—it’s irreversible, so don't mess around.

Inspecting Components and Media Assets

Want to see what kind of structures are possible? Run list_components to get a full list of every available content component blueprint; this shows you exactly what structures your site can handle. To check out the media, use list_assets, which fetches a complete inventory of every single media file stored in the Storyblok space, giving you both their URLs and metadata.

Auditing Permissions

If you gotta check who's allowed into the system, run list_space_users to get an account list of everyone with access permissions to the current space. This keeps your security tight.

Basically, you use these tools to build a complete picture of what’s going on behind the curtain. You don't have to rely on clicks; you control the data flow using simple commands like create_content_story(name: string, slug: string, content: JSON) or checking existing assets with list_assets().