Storyblok Use MCP
Use when interacting with Storyblok through the MCP server — the tool model, operation names and payload shapes for stories, assets, components, datasources and every other resource. Load it before calling `mcp__storyblok__` tools, alongside the skill that owns the task.
Install
/plugin marketplace add storyblok/agent-pluginThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add storyblok/agent-plugin --skill storyblok-use-mcpgit clone --depth 1 https://github.com/storyblok/agent-plugin.git /tmp/agent-plugin
mkdir -p ~/.claude/skills
cp -r /tmp/agent-plugin/skills/storyblok-use-mcp ~/.claude/skills/storyblok-use-mcpPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Work with Storyblok through the MCP server ## Inputs `space_id` (integer) is required on nearly every operation, and it is all you need — the server derives the region from it. `listSpaces` and the few other operations taking no `space_id` have nothing to derive from: `describe` marks them `requiresRegion`, and they need `region` passed explicitly even when it is `eu`. Never infer the region from project files — get a `space_id` instead, or ask the user. ## Tool model Most of the API runs through **generic executors** taking an `operation` name plus `parameters`: | Tool | For | | ------------------------------------- | ---------------------------------------------------- | | `mcp__storyblok__execute_readonly` | reads (`listStories`, `getStoryById`, `listAssets`…) | | `mcp__storyblok__execute_mutating` | creates and updates | | `mcp__storyblok__execute_destructive` | deletes | | `mcp__storyblok__search` / `describe` | finding operations and their parameter schemas | `describe` returns an operation's executor as `executeWith`. Mind the argument names: the executors take `operation`, `describe` takes `operationId`. `mcp__storyblok__upload_asset` and `mcp__storyblok__upload_asset_finish` are **standalone tools, not operations**. `describe` on them returns
Details
- Skill name
storyblok-use-mcp- Repository
- storyblok/agent-plugin
- Path
skills/storyblok-use-mcp/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Storyblok Use MCP skill do?
Use when interacting with Storyblok through the MCP server — the tool model, operation names and payload shapes for stories, assets, components, datasources and every other resource. Load it before calling `mcp__storyblok__` tools, alongside the skill that owns the task.
How do I install the Storyblok Use MCP skill?
Claude Code plugin: /plugin marketplace add storyblok/agent-plugin. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Storyblok Use MCP popular?
It lives in storyblok/agent-plugin, which has 9 GitHub stars and 0 forks.
Related skills
Storyblok Build Frontend
9storyblok/agent-plugin
Use when generating frontend components for Storyblok blocks — writing, registering and validating the framework code that renders a space's content. E.g. "generate components for my blocks", "build an Astro + Storyblok landing page".
Storyblok Build Plugin
9storyblok/agent-plugin
Use when extending Storyblok with plugins to enhance what editors can do — custom field inputs, Visual Editor panels, pages inside a space, integrations with external systems — including choosing, building, or deploying one. E.g. "editors need a map location picker", "build a field plugin", "deploy our plugin".
Storyblok Implement Figma
9storyblok/agent-plugin
Use when turning a Figma design into frontend components backed by Storyblok blocks. E.g. "figma to storyblok", "build this Figma design".
Agent Builder
5NikolasMarkou/agent-builder
Build, review, troubleshoot, optimize, and extend AI agents — single-agent, multi-agent, RAG, and production systems. Covers framework selection, pattern selection (topology, behavioral, data flow), agent orchestration, state design, and tool design. Defaults to Python with LangChain/LangGraph; also supports CrewAI, Strands, OpenAI Agents SDK, Google ADK, and Mastra. Use whenever the user wants to build, design, scaffold, review, debug, optimize, extend, or migrate an agent or agentic system.
Recover Semantic Model
9kr4chinin/skills
Recover a program's minimal semantic model (the state that changes what users see, how its transitions repeat and reorder, what each effect requires). Use when asked to recover or audit that model, to check what is idempotent or order-dependent, or to split a refactor into provably equivalent and "trust me" changes.
Agent Design Fundamentals
10Archive228/lab-skills
Decision rules for whether to build an LLM agent and how to architect it, distilled from OpenAI's "A Practical Guide to Building Agents": build/no-build criteria, model selection, tool design, single-agent vs multi-agent orchestration (manager pattern vs decentralized handoffs), layered guardrails, and human-in-the-loop triggers. Use when designing, reviewing, or refactoring an agent system — before choosing an architecture, adding more agents, defining tools, or shipping an agent to production without guardrails.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.