storyblok

This MCP server exposes Storyblok Management API capabilities as MCP tools. It lets AI assistants execute content operations, manage components and schemas, handle assets, and coordinate workflow steps and releases against a Storyblok space using a typed, MCP-friendly interface. The server is designed to be consumed by MCP clients and supports a wide range of modules such as Stories, Components, Assets, Workflows, Releases, and more, all surfaced through a consistent set of tool calls with strict schemas for safety and predictability. Start by providing the proper environment tokens and space ID, then invoke the available tools via an MCP client to create, read, update, delete, bulk modify content, manage permissions, and trigger releases or workflows as needed. Tools expose operations like CRUD on stories and components, bulk updates, publishing, versioning, asset uploads, tag management, webhook configuration, and workflow management, all mapped to Storyblok's Management API endpoints.

Prerequisites:

• Node.js 20+ installed on the host
• Access to a Storyblok space with Management token and a public/preview token

Installation steps:

1. Clone the repository: git clone https://github.com/hypescale/storyblok-mcp-server.git
2. Install dependencies: cd storyblok-mcp-server npm install
3. Configure environment variables (example provided by .env.example): STORYBLOK_SPACE_ID=your_space_id STORYBLOK_MANAGEMENT_TOKEN=your_management_token STORYBLOK_DEFAULT_PUBLIC_TOKEN=your_public_token
4. Build the project (if applicable): npm run build
5. Run the server: npm run start
6. Connect via an MCP client using the generated configuration (see “Usage with MCP Clients” in the README for example client configs).

Tips and considerations:

• Use the minimum required permissions for STORYBLOK_MANAGEMENT_TOKEN to reduce risk.
• Ensure the Space ID is numeric and tokens correspond to the correct Storyblok space.
• The server exposes a large surface area (160+ tools across 30 modules); consider enabling or disabling modules as needed for security and performance.
• Keep the Node.js runtime updated to satisfy the >= 20 requirement and to benefit from performance and security improvements.
• When integrating with MCP clients (Claude, Codex, Cursor, Windsurf, VS Code, etc.), follow the config examples precisely and ensure environment variables are propagated to the runtime process.
• For local development, use hot-reload and type-check workflows if provided (npm run dev, npm run typecheck).