Storyblok MCP Server

Storyblok MCP Server

A Storyblok MCP Server built on TypeScript with more than 130+ Actions

Category
访问服务器

README

Storyblok MCP Server

License: MIT Node.js MCP TypeScript

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

Find all stories updated in the last 7 days and tag them as "reviewed".

Response (example)

Found 12 stories updated since 2025-12-28.
Applied tag "reviewed" to 12 stories.

Quick Start

# Clone the repository
git clone https://github.com/hypescale/storyblok-mcp-server.git
cd storyblok-mcp-server

# Install dependencies
npm install

# Build
npm run build

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

cp .env.example .env

Then start the server:

npm run start

Requirements

  • Node.js >= 20
  • A Storyblok space with Management + Public/Preview tokens

Configuration

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

STORYBLOK_SPACE_ID=your_space_id
STORYBLOK_MANAGEMENT_TOKEN=your_management_token
STORYBLOK_DEFAULT_PUBLIC_TOKEN=your_public_token

What they are used for:

Variable Description
STORYBLOK_SPACE_ID Your numeric Storyblok space ID
STORYBLOK_MANAGEMENT_TOKEN Management API token with appropriate permissions
STORYBLOK_DEFAULT_PUBLIC_TOKEN Public/Preview token for content delivery

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

<details> <summary>Show config</summary>

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "storyblok": {
      "command": "node",
      "args": ["/path/to/storyblok-mcp-server/dist/index.js"],
      "env": {
        "STORYBLOK_SPACE_ID": "your_space_id",
        "STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
        "STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
      }
    }
  }
}

</details>

Codex CLI / IDE

<details> <summary>Show config</summary>

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

codex mcp add storyblok \
  --env STORYBLOK_SPACE_ID=your_space_id \
  --env STORYBLOK_MANAGEMENT_TOKEN=your_management_token \
  --env STORYBLOK_DEFAULT_PUBLIC_TOKEN=your_public_token \
  -- node /path/to/storyblok-mcp-server/dist/index.js

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

[mcp_servers.storyblok]
command = "node"
args = ["/path/to/storyblok-mcp-server/dist/index.js"]

[mcp_servers.storyblok.env]
STORYBLOK_SPACE_ID = "your_space_id"
STORYBLOK_MANAGEMENT_TOKEN = "your_management_token"
STORYBLOK_DEFAULT_PUBLIC_TOKEN = "your_public_token"

</details>

Cursor

<details> <summary>Show config</summary>

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

{
  "mcpServers": {
    "storyblok": {
      "command": "node",
      "args": ["/path/to/storyblok-mcp-server/dist/index.js"],
      "env": {
        "STORYBLOK_SPACE_ID": "your_space_id",
        "STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
        "STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
      }
    }
  }
}

</details>

Windsurf

<details> <summary>Show config</summary>

Create ~/.codeium/mcp_config.json:

{
  "mcpServers": {
    "storyblok": {
      "command": "node",
      "args": ["/path/to/storyblok-mcp-server/dist/index.js"],
      "env": {
        "STORYBLOK_SPACE_ID": "your_space_id",
        "STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
        "STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
      }
    }
  }
}

</details>

VS Code

<details> <summary>Show config</summary>

Create .vscode/mcp.json in your workspace:

{
  "servers": {
    "storyblok": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/storyblok-mcp-server/dist/index.js"],
      "env": {
        "STORYBLOK_SPACE_ID": "your_space_id",
        "STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
        "STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
      }
    }
  }
}

</details>

Continue

<details> <summary>Show config</summary>

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

name: Storyblok MCP
version: 1.0.0
schema: v1
mcpServers:
  - name: storyblok
    command: node
    args:
      - /path/to/storyblok-mcp-server/dist/index.js
    env:
      STORYBLOK_SPACE_ID: your_space_id
      STORYBLOK_MANAGEMENT_TOKEN: your_management_token
      STORYBLOK_DEFAULT_PUBLIC_TOKEN: your_public_token

</details>

Cline

<details> <summary>Show config</summary>

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

{
  "mcpServers": {
    "storyblok": {
      "command": "node",
      "args": ["/path/to/storyblok-mcp-server/dist/index.js"],
      "env": {
        "STORYBLOK_SPACE_ID": "your_space_id",
        "STORYBLOK_MANAGEMENT_TOKEN": "your_management_token",
        "STORYBLOK_DEFAULT_PUBLIC_TOKEN": "your_public_token"
      }
    }
  }
}

</details>

Available Tools

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

Module Tools Description
Stories 18 CRUD, bulk operations, publishing, versioning
Components 9 Schema management, versioning, usage tracking
Assets 9 Upload, organize, bulk operations
Workflows 6 Workflow management and stages
Releases 5 Release scheduling and deployment
Datasources 5 Key-value data management
Tags 5 Content tagging and organization
Webhooks 5 Event notifications
Collaborators 4 Team management
Space Roles 5 Permissions and access control
... ... And 20+ more modules

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

# Run in development mode with hot reload
npm run dev

# Type check
npm run typecheck

# Build for production
npm run build

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

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选