Storyblok MCP Server

Other

Storyblok splits content into stories, components, and assets, and most of the day-to-day work in it is finding the right story and checking what's actually live versus what's still a draft. Connect Storyblok to Neotask and the agent browses your space directly, pulls a story's current fields, and reads published content back through the content delivery API when you need to know what's showing on the live site right now, not what's sitting in the editor.

• Browses stories, components, and assets in a connected Storyblok space
• Pulls published content through the content delivery API for use in an app or a quick check
• Answers "what does the live page actually say" without opening the Storyblok editor

What you can automate

Storyblok MCP Server

Developers and editors can browse and manage content stories, components, and assets in a Storyblok space, and pull published content through the content delivery API for use in an application.

Real workflows

Check what a story looks like once published

Ask what a specific story or component currently renders on the live site; the agent reads it through the content delivery API and reports the actual published fields, not the draft.

Audit a content structure before a build

Ask which components and assets exist in a space before wiring up a new page template; the agent lists what is there so you are not guessing at field names.

Frequently asked questions

Does this only read drafts, or published content too?

Both — it can browse stories and components in the space, and it pulls the actual published version through the content delivery API when you need what is live.

Do I still need the Storyblok editor?

For visual editing, yes. For checking, listing, or pulling content into another workflow, Neotask can do that from a conversation.