← All integrations

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.

Runs once, when you ask

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

Connect Storyblok to Claude, ChatGPT or Cursor

  1. 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. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, 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. 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.