Storyblok MCP Server

Storyblok MCP becomes available to MCP clients through the storyblok mcp mcp server. MCP server for Storyblok integration.

What Storyblok MCP does

Connect AI tools to Storyblok instantly - use natural language to manage your CMS like magic.

Storyblok is a powerful headless CMS. API-first. Easy for devs and content creators to work together.

Installing the storyblok mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 4 environment variables: STORYBLOK_SPACE_ID, STORYBLOK_MANAGEMENT_TOKEN, STORYBLOK_DEFAULT_PUBLIC_TOKEN, GOOGLE_GENERATIVE_AI_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Storyblok MCP sits in that group. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by ArjunCodess, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the storyblok mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.