Storyblok MCP Server for Cursor 9 tools — connect in under 2 minutes
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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.
{
"mcpServers": {
"storyblok": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
Cursor's Agent mode turns Storyblok into an in-editor superpower. Ask Cursor to generate code using live data from Storyblok and it fetches, processes, and writes. all in a single agentic loop. 9 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Space & Content Discovery — Instantly list active enterprise environments utilizing
list_spacesand fetch broad overarching overviews referencing stories vialist_stories. - Content Construction — Swiftly produce or update textual assets creating schemas directly from prompts invoking
create_content_storyandupdate_content_storysystematically. - Asset & Structure Exploration — Analyze media repositories via
list_assetsand precisely inspect available schema blueprints callinglist_componentsto 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 Cursor 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 Cursor via MCP
Follow these steps to integrate the Storyblok MCP Server with Cursor.
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
Save the file
Cursor will automatically detect the new MCP server
Start using Storyblok
Open Agent mode in chat and ask: "Using Storyblok, help me...". 9 tools available
Why Use Cursor with the Storyblok MCP Server
Cursor AI Code Editor provides unique advantages when paired with Storyblok through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Storyblok + Cursor Use Cases
Practical scenarios where Cursor combined with the Storyblok MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Storyblok MCP Tools for Cursor (9)
These 9 tools become available when you connect Storyblok to Cursor 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 Cursor
Ready-to-use prompts you can give your Cursor 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 Cursor
Common issues when connecting Storyblok to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Storyblok + Cursor FAQ
Common questions about integrating Storyblok MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.Can Cursor use MCP tools in inline edits?
How do I verify MCP tools are loaded?
Connect Storyblok with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Storyblok to Cursor
Get your token, paste the configuration, and start using 9 tools in under 2 minutes. No API key management needed.