How does the AI validate JSON payloads before creating content?

Instruct the agent to call `list_components` first. It returns the exact field names and types each component expects, so the AI builds a compliant JSON payload before calling `create_content_story`.

Can the agent accidentally delete entire spaces?

No. `delete_content_story` targets a single story by ID — it cannot perform recursive or bulk deletions. For extra safety, use a token scoped with limited write permissions.

What content types can I manage through this integration?

Stories (pages, articles, blog posts), media assets (images, videos, documents), component definitions, and space-level settings. Use `list_stories`, `list_assets`, and `list_components` to explore your content.

Storyblok MCP Server for Claude Desktop 9 tools — connect in under 2 minutes

Name: Storyblok
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 9 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Storyblok and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "storyblok": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Storyblok MCP Server

Integrate the powerful headless CMS capabilities of Storyblok directly into your conversational AI. Empower your content teams and developers to organically draft narratives, parse complex asset repositories, and orchestrate page component definitions without relying entirely on the visual editor. Bind your AI local context directly to your Storyblok environment securely, enabling programmatic schema generation and continuous iteration utilizing a streamlined conversational interface designed to accelerate creative velocity.

Claude Desktop is the definitive way to connect Storyblok to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 9 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Space & Content Discovery — Instantly list active enterprise environments utilizing list_spaces and fetch broad overarching overviews referencing stories via list_stories.
Content Construction — Swiftly produce or update textual assets creating schemas directly from prompts invoking create_content_story and update_content_story systematically.
Asset & Structure Exploration — Analyze media repositories via list_assets and precisely inspect available schema blueprints calling list_components to standardize development.
Risk Management — Exercise safe administrative control over local projects, evaluating internal authorized operators implementing modifications using list_space_users.

The Storyblok MCP Server exposes 9 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Storyblok to Claude Desktop via MCP

Follow these steps to integrate the Storyblok MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Storyblok

Look for the 🔌 icon in the chat — your 9 tools are now available

Why Use Claude Desktop with the Storyblok MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Storyblok through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Storyblok + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Storyblok MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Storyblok MCP Tools for Claude Desktop (9)

These 9 tools become available when you connect Storyblok to Claude Desktop via MCP:

create_content_story

Provide a name, slug, and content JSON. Creates a new story in a Storyblok space

delete_content_story

This action is irreversible. Permanently deletes a Storyblok story

get_story_details

Retrieves details for a specific content story

list_assets

Lists media assets in a Storyblok space

list_components

Lists available content components

list_space_users

Lists all users with access to a specific space

list_spaces

Lists all accessible Storyblok spaces

list_stories

Requires a space ID. Lists content stories within a specific space

update_content_story

Requires space and story IDs. Updates fields of an existing Storyblok story

Example Prompts for Storyblok in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Storyblok immediately.

"List the recent articles from my Storyblok space and detail their structural components."

"List the structure blueprints by calling list_components and then formulate a new JSON to create a blog story."

"List all multimedia assets in my Storyblok space and display their URLs."

Troubleshooting Storyblok MCP Server with Claude Desktop

Common issues when connecting Storyblok to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Storyblok + Claude Desktop FAQ

Common questions about integrating Storyblok MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.