Integration · Automate and collaborate

Storyblok and Meteor AI agents

Connect Storyblok to a WhatsApp Met: find the Management API operation and read your stories with Storyblok's official MCP.

Book a demo See every integration

How does Storyblok connect to Meteor?

With the Storyblok ready connector, your WhatsApp Met uses Storyblok's official MCP server with the account the admin authorizes. The server does not have one tool per action: the Met searches for the Management API operation it needs, reads which parameters it takes and runs it with the matching read, write or delete tool. That way it lists and gets your stories. The write and delete tools start turned off: if the admin turns on the write tool, the Met creates and updates stories, and when updating one, Storyblok lets it publish in the same step, and then the change goes live on your site.

What it automates

What a Meteor Met does with Storyblok

Change a promotion's text or price

The owner sends the Met the change. If the admin turned on the write tool, which starts turned off, the Met finds the promotion's story, updates it and, depending on what the skill says, publishes it in the same step or saves it unpublished.

Check what a story says

The Met finds the read operation, gets the story and answers with what it says, asking only for the fields it needs so it does not pull more than necessary.

Review the stories in a folder

The Met lists the stories in a folder, such as the active promotions, with their name and slug, so the team sees which promotions exist.

Prepare a new story

Writing starts turned off. If the admin turns it on, the Met creates a new story with the content the team sends, saved unpublished so someone can review it in Storyblok.

7 tools

Everything your Met can ask Storyblok for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`search`	Finds Management API operations by keyword, with their ID, behavior hints, summary and available response fields.
`describe`	Gets all of an operation's parameters and the body schema for write operations, and says which execute_ tool to use.
`execute_readonly`	Runs safe read operations (GET) on the Management API, to list and get resources.
`execute_mutating`	Runs operations that change data (POST, PUT, PATCH), to create and update resources. Starts turned off.
`execute_destructive`	Runs destructive operations (DELETE) on the Management API. Starts turned off.
`upload_asset`	Creates an asset record and returns a signed S3 upload URL with a ready to use cURL command.
`upload_asset_finish`	Finalizes and validates the asset upload to S3, done with cURL or by hand.

The limits

What the Storyblok integration does NOT do

We would rather say it here than have you find out during rollout.

It does not read published content through the Content Delivery API: the server only exposes the Management API.
It does not finish file uploads: Storyblok states that finishing one needs a console to send the file with the cURL command, and the Met has no console.
It does not delete unless the admin turns it on: execute_destructive starts turned off. Storyblok advises against running deletions in autonomous automation, so it is best to leave it that way.
It does not ask you for confirmation in the chat before writing or publishing. Writing and deleting start turned off; if the admin turns them on in Connections, the Met runs them.
It is not meant for bulk, repeatable changes: Storyblok points to its CLI for that, and the server's calls count against the Management API rate limits.
It does not pay your Storyblok plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Storyblok

1

A Storyblok account with access to the space

Your team's Storyblok account. Storyblok advises limiting the connection to the spaces and permissions you need, and testing first in a sandbox space.
2

Connect it in Met

In Met, open Connections → Storyblok → Connect. A Storyblok window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about Storyblok and Meteor

Because Storyblok's server requires it: search finds the operation, describe gives its parameters and the matching execute_ tool runs it.

Writing starts turned off, so nothing changes until the admin turns it on. With it on, it depends on how it updates the story: Storyblok lets it publish in the same step or save without publishing. Put it in the skill.

It can start the upload but not finish it: the file is sent with a cURL command from a console, and someone on the team does that.

You do, with your Storyblok account and plan. Meteor does not resell Storyblok or charge for the actions your Met takes there.

Step by step