Storyblok MCP server
43 operations0 webhooks
Headless CMS content from Storyblok - manage stories, components, datasources and their entries, tags, asset metadata, releases and webhook endpoints through the Management API.
Try Storyblok with your agent
Connect Storyblok, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Storyblok on my account, then run one read-only example and show me the result.
Storyblok tools and triggers
Tools are what your agent can do in Storyblok through Corsair's MCP server. Triggers are the Storyblok events a routine can start from.
Stories
- CreateWrite
Create a story, optionally publishing it or grouping it in a release in the same call
stories.create
- DeleteDestructive
Delete a story and trash it. Storyblok keeps it in the trash, but this plugin does not wrap a restore, so treat it as permanent
stories.delete
- GetRead-only
Read one story with its full content, published state, tags and version ids
stories.get
- ListRead-only
List stories with filters for slug, tag, parent, publication state and release. This route omits each story's content unless with_summary is set
stories.list
- PublishWrite
Publish a story, or add it to a release with release_id. Storyblok implements this as a GET, but it changes published state
stories.publish
- UnpublishWrite
Unpublish a story, so the Content Delivery API stops serving it. Storyblok implements this as a GET
stories.unpublish
- UpdateWrite
Replace a story's fields and content. Sending publish also publishes it; without it the change stays a draft
stories.update
Webhooks
- CreateWrite
Register a webhook endpoint for the given actions, optionally with a secret Storyblok signs each delivery with
webhooks.create
- DeleteDestructive
Delete a webhook endpoint, so Storyblok stops posting to its URL
webhooks.delete
- GetRead-only
Read one webhook endpoint with its actions and activation
webhooks.get
- ListRead-only
List the webhook endpoints on the space
webhooks.list
- List ActionsRead-only
List the action names a webhook may subscribe to, read from Storyblok so a new event needs no plugin change
webhooks.listActions
- UpdateWrite
Replace a webhook endpoint, its action list or its activation
webhooks.update
Assets
- Bulk DeleteDestructive
Delete several assets in one call, with the same effect as deleting each
assets.bulkDelete
- DeleteDestructive
Delete one asset, so any content referencing it shows a broken file
assets.delete
- GetRead-only
Read one asset with its file details and metadata
assets.get
- ListRead-only
List assets with a search and a folder filter
assets.list
- UpdateWrite
Change an asset's metadata: alt text, title, copyright, focus point, privacy and publish window. Uploading new bytes is a separate flow and is not wrapped
assets.update
Datasource Entries
- CreateWrite
Add an entry to a datasource
datasourceEntries.create
- DeleteDestructive
Delete a datasource entry; content using that option loses it
datasourceEntries.delete
- GetRead-only
Read one datasource entry with its name, value and position
datasourceEntries.get
- ListRead-only
List datasource entries, optionally only those of one datasource or one dimension value
datasourceEntries.list
- UpdateWrite
Replace a datasource entry's name and value
datasourceEntries.update
Datasources
- CreateWrite
Create a datasource, whose slug is what content uses to reference it
datasources.create
- DeleteDestructive
Delete a datasource along with its entries. Content that references it is left pointing at nothing
datasources.delete
- GetRead-only
Read one datasource with its dimensions
datasources.get
- ListRead-only
List the datasources on the space, such as reusable option lists
datasources.list
- UpdateWrite
Replace a datasource name and slug
datasources.update
Releases
- CreateWrite
Create a release that stories can be grouped into and published together
releases.create
- DeleteDestructive
Delete a release. The stories grouped in it stay, but the grouping is gone
releases.delete
- GetRead-only
Read one release with its schedule, released state and the branches it deploys
releases.get
- ListRead-only
List releases with their schedules and released state
releases.list
- UpdateWrite
Change a release, or publish it in the same call with do_release
releases.update
Components
- CreateWrite
Create a component, which is the field schema a content type uses. Its name is the key content references
components.create
- DeleteDestructive
Delete a component. Content that uses it can no longer render, and this cannot be undone
components.delete
- ListRead-only
List the components that define content types, with their field schemas
components.list
- UpdateWrite
Replace a component's field schema. Existing content is not migrated: a removed field's values stay in stories, hidden, until a migration removes them
components.update
Tags
- CreateWrite
Create a tag, optionally attaching it to a story as it is created
tags.create
- DeleteDestructive
Delete a tag, removing it from every story that carried it. This cannot be undone
tags.delete
- ListRead-only
List the tags on the space with how many stories carry each
tags.list
- UpdateWrite
Rename a tag, which updates every story that carries it
tags.update
Spaces
- GetRead-only
Read the configured space: its plan, counts, environments and defaults
spaces.get
- ListRead-only
List the spaces the token can reach, which is how a space id is found
spaces.list
Connect Storyblok to Claude, ChatGPT or Cursor
- 1
Connect Storyblok in Corsair
Add your Storyblok API key once in Corsair. Corsair stores the credential encrypted and makes the Storyblok API calls for your agent, so it never goes into a prompt or a config file. Connect Storyblok
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Storyblok. On a ChatGPT personal plan, connect Storyblok here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Storyblok's read and write operations run right away and its 9 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/storyblok, add the Storyblok plugin, and connect with an API key. Then call methods like corsair.storyblok.api.assets.bulkDelete() from your app. Corsair keeps each tenant isolated.
Yes. Storyblok requires an API key from your Storyblok account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Storyblok, GitHub, Notion, Stripe, and the rest. Trigger Storyblok from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for headless CMS content from Storyblok - manage stories, components, datasources and their entries, tags, asset metadata, releases and webhook endpoints through the Management API. Common builds include sync jobs, admin tooling, and agents that call Storyblok APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Storyblok API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/storyblok in the open repo. When Storyblok ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Storyblok data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Storyblok data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Storyblok on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 9 destructive Storyblok operations. You can change a link's mode at hub.corsair.dev/me.