Storyblok Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

MCP server for Storyblok: stories, spaces. Needs an API token.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server that connects an assistant to Storyblok so it can work with stories and spaces in a Storyblok account.

What you can do
Work with Storyblok stories, such as listing, reading or managing content entries through the assistant. Access Storyblok spaces to browse or operate on the content areas of an account. The exact set of tools is not documented in the supplied material, so capabilities beyond stories and spaces are unconfirmed.
When to use it
Useful when you manage Storyblok content and want an assistant to read or act on stories and spaces without switching to the Storyblok interface.
Requirements
Runs as a local process on the user's machine, installed from the npm package, so Node.js and npm are needed. A Storyblok API token is required according to the description, though the manifest declares no environment variables or headers.
Before you install
The server needs a Storyblok API token, which is a credential for your content account; keep it private and prefer a scoped or read-only token where possible. Tools may change content in stories and spaces, so review write actions before allowing them. The manifest declares no authentication configuration, so how the token is supplied is unclear.

Installation

In SourceWeft

  1. Open Storyblok Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 17, 2026
  2. v1.0.0Sep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.