---
title: "storyblok"
description: "Agentic content operations for Storyblok: model blocks, author pages, populate content at volume, set up translations, and publish safely, via the Storyblok MCP server for interactive edits and the Storyblok CLI for repr"
canonical: https://agentpluginsdirectory.com/plugins/storyblok
last-updated: 2026-09-09
---

# storyblok
Agentic content operations for Storyblok: model blocks, author pages, populate content at volume, set up translations, and publish safely, via the Storyblok MCP server for interactive edits and the Storyblok CLI for reproducible bulk work.
- Slug: storyblok
- Publisher: Owen Ayres
- Repository: https://github.com/oayres/agent-plugins
- Manifest: plugins/storyblok/plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): other
- Skills: 7 (storyblok-authoring, storyblok-content-modelling, storyblok-content-population, storyblok-frontend-sync, storyblok-i18n, storyblok-publishing, storyblok)
- MCP servers: 1 (storyblok)
- Stars: 0
- Repository created: 2026-09-08
- Repository last pushed: 2026-09-08
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/storyblok
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What storyblok does, in the publisher's words

An agent plugin for operating a Storyblok space: model blocks, author pages, populate content at volume, set up translations, and publish safely.

- Two channels, chosen per task: the hosted Storyblok MCP server for interactive edits and exploration; the Storyblok CLI v4 or a short Management API script for bulk, reproducible, and CI-friendly work
- Survey, plan, confirm once, execute, verify: every mutating flow reads the space first, states a plan naming anything that will be published or deleted, gets one confirmation, then reads back the result
- Draft by default: authoring and imports never publish; publishing is its own skill with its own confirmation, and batches go through releases

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/oayres/agent-plugins/HEAD/plugins/storyblok/README.md

## Skills

- storyblok-authoring: Create and edit Storyblok stories (pages and entries) from existing blocks. Use proactively when the user asks to create a page, when writing an article or landing page in Storyblok, when adding or reordering sections on a page, when fixing a slug or moving a story to another folder, when setting S…
- storyblok-content-modelling: Design and change Storyblok components (blocks). Use proactively when the user asks to add a block, when creating a content type, when adding or renaming a field, when restricting which blocks can nest where, when setting up presets or component folders, when marking fields translatable, or when a…
- storyblok-content-population: Bring content into Storyblok at volume. Use proactively when the user asks to import, migrate, seed, or bulk-create stories, assets, or datasource entries, when the source is markdown, CSV, JSON, an existing website, another Storyblok space, or generated placeholder content, when copying content be…
- storyblok-frontend-sync: Keep a frontend codebase in step with a Storyblok space. Use proactively when the user asks to generate TypeScript types from Storyblok components, when registering or mapping blocks to React, Next.js, Astro, Nuxt, Vue, or Svelte components, when finding blocks with no frontend component (or compon…
- storyblok-i18n: Set up and operate translations in Storyblok. Use proactively when the user mentions languages, locales, translation, localisation, i18n, or multi-region content, when setting up a new language for a space, when translating a story or a folder, when configuring translated slugs, or when checking ho…
- storyblok-publishing: Publish, unpublish, schedule, and release Storyblok content safely. Use proactively when the user asks to publish or go live, when unpublishing or taking content down, when scheduling content for a date, when creating or deploying a release, when moving a story through workflow stages, or when any…
- storyblok: Core workflow for any Storyblok content task. Use proactively when the user mentions Storyblok, a Storyblok space, blocks or bloks, content types, stories, or the Visual Editor, when creating, editing, translating, or populating CMS content in a project that uses Storyblok, when publishing or sched…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- storyblok: transport: streamable-http; url: https://mcp.storyblok.com/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.