Storyblok MCP Server

A TypeScript Model Context Protocol server for the Storyblok Management API. It lets AI assistants and agents manage Storyblok content, workflows, and configuration safely and programmatically.

Why this project

Storyblok is powerful, but repetitive content operations and release workflows can be time-consuming. This server bridges MCP-compatible assistants with Storyblok so teams can:

• Automate content ops (bulk updates, tagging, assets)

• Orchestrate releases and workflows with less manual effort

• Keep component libraries and schemas consistent

• Give AI agents structured, typed access to Storyblok

Highlights

• 160 tools across 30 modules mapped to Storyblok Management API capabilities

• Typed schemas with Zod for safer tool calls

• MCP-first design for MCP-compatible clients

• Simple config using environment variables

What it does in 15 seconds

Prompt

Response (example)

Quick Start

Create a .env file from the example and fill in your credentials:

Then start the server:

Requirements

• Node.js >= 20

• A Storyblok space with Management + Public/Preview tokens

Configuration

The server requires three environment variables (see .env.example):

What they are used for:

Tip: Use the smallest permission set possible for safety.

Usage with MCP Clients

This server is designed to work with any MCP-compatible client. Here are ready-to-copy configs for popular tools.

Claude Desktop

Add to your claude_desktop_config.json:

Codex CLI / IDE

Codex supports MCP servers via CLI or by editing ~/.codex/config.toml. The CLI and IDE extension share the same config.

Option A: Configure with the Codex CLI

Option B: Configure with ~/.codex/config.toml

Cursor

Create a project config at .cursor/mcp.json (or use the global config at ~/.cursor/mcp.json):

Windsurf

Create ~/.codeium/mcp_config.json:

VS Code

Create .vscode/mcp.json in your workspace:

Continue

Create a YAML config at .continue/mcpServers/storyblok.yaml:

Cline

Open Cline settings and use "Configure MCP Servers" to open cline_mcp_settings.json, then add:

Available Tools

The tool surface mirrors Storyblok's Management API. Total tool count and modules are defined in src/tools/index.ts.

Example Prompts

Use these prompts in your MCP client to see quick wins:

• "List all stories updated in the last 7 days and tag them as 'reviewed'."

• "Create a release for next Friday and add the homepage and pricing stories."

• "Find unused components and tell me which stories still reference them."

• "Upload these assets and organize them into a new 'Campaign' folder."

Development

Project Structure

• src/index.ts - MCP server entry point

• src/tools/* - Tool modules mapped to Storyblok API areas

• src/types/* - Shared API and Storyblok types

• src/utils/* - HTTP helpers and response formatting

• src/config.ts - Environment configuration and validation

Troubleshooting

• ConfigError: STORYBLOK_* is missing - ensure .env is present and filled out.

• 401 Unauthorized - verify the Management and Public/Preview tokens.

• 404 Not Found - double-check the STORYBLOK_SPACE_ID.

Tech Stack

• TypeScript with strict type checking

• @modelcontextprotocol/sdk for MCP implementation

• Zod for runtime schema validation

• Native fetch API for HTTP requests

Release and Versioning

When you're ready to cut a release:

1. Update package.json version (semantic versioning recommended).

2. Update README.md if behavior or setup changed.

3. Tag the release and publish a GitHub Release with notes.

This keeps the project easy to consume for open source users and downstream tools.

Security Notes

• Never commit .env files or tokens to git.

• Prefer tokens scoped to a dedicated Storyblok space for automation.

• Rotate tokens if you suspect exposure.

Contributing

Issues and PRs are welcome. If you're planning a large change, open an issue first so we can align on scope and direction.

License

MIT

Built by hypescale | Maintained by Martin Kogut