Storyblok MCP server
Storyblok in any MCP client, through Memtro: Storyblok does not publish this server. Memtro's Storyblok connector reads Storyblok through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Storyblok: the stories (pages) in a space with their text, assets, datasources and entries, the space's activity log, and the discussions on a story; can create, update, publish, unpublish, schedule, duplicate and delete stories, start, reply to and resolve discussions, change datasource entries, and delete assets.
Reads
storyblok_list_storiesStories (pages and entries) in the Storyblok space, without their body: name, full slug, published state, unpublished changes, dates…storyblok_get_storyOne Storyblok story by id: its fields, content type, and the text of its content (rich text and text fields, cut to 4,000 characters).storyblok_list_assetsAssets (images, files) in the Storyblok space: file name and address, type, size, alt text, title, copyright, privacy and dates.storyblok_list_datasourcesDatasources in the Storyblok space (lists of key and value pairs used by the content, such as categories or labels), with their ids and slugs.storyblok_datasource_entriesEntries of one Storyblok datasource: name, value, and the value in a dimension (e.g. a language) when one is given.storyblok_recent_activityThe Storyblok space's activity log: who changed, published or commented on what, newest first.storyblok_story_discussionsDiscussions (comment threads on a field) on one Storyblok story: title, field, component, language, whether solved, and the last comment's text.
Acts, when you ask
These change something in Storyblok. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
storyblok_create_storyCreate a Storyblok story (or a folder) in the space.storyblok_update_storyChange a Storyblok story's name, slug, tags, folder or content.storyblok_publish_storyPublish a Storyblok story so its current version goes live on the delivery API and the site.storyblok_unpublish_storyUnpublish a Storyblok story so it leaves the delivery API and the live site (it stays as a draft).storyblok_delete_storyPermanently delete a Storyblok story (or an empty folder).storyblok_duplicate_storyCopy a Storyblok story, as a new draft, into a folder (for example a language folder).storyblok_schedule_story_publishSchedule a Storyblok story to publish at a future time, when it goes live on the site without anyone acting.storyblok_create_discussionStart a discussion (a comment thread) on one field of a block in a Storyblok story, with a first comment in plain text.storyblok_reply_to_discussionAdd a plain-text comment to an existing Storyblok discussion.storyblok_resolve_discussionMark a Storyblok discussion resolved, now.storyblok_create_datasource_entryAdd a key and value entry to a Storyblok datasource.storyblok_update_datasource_entryChange a Storyblok datasource entry's key or value, or its value in one dimension (e.g. a language).storyblok_delete_datasource_entryPermanently delete a Storyblok datasource entry.storyblok_delete_assetDelete a Storyblok asset from the space's media library.
Connect it
First connect Storyblok on Dashboard → Connections, then add Memtro to your client once. The Storyblok tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Storyblok connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What changed on the pricing page this week?
- › Which blog stories have unpublished changes?
- › Which discussions on the homepage are still unsolved?
- › Which images have no alt text?
- › Schedule the spring launch story to publish at 9am on Monday.
Questions
- Is this an official Storyblok MCP server?
- No. It is Memtro's MCP server with Memtro's Storyblok connector behind it: the connector reads Storyblok through its API with the credentials you connect on Dashboard → Connections, and Storyblok publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Storyblok?
- Only when you ask, and only what it has been granted: create a Storyblok story or folder (a draft unless publish is set); update a Storyblok story (optionally publishing it); publish a Storyblok story (live on the site); unpublish a Storyblok story (taken off the site); delete a Storyblok story (permanent); duplicate a Storyblok story into a folder; schedule a Storyblok story to publish; start a discussion on a Storyblok story field; reply to a Storyblok discussion; resolve a Storyblok discussion; add a Storyblok datasource entry; change a Storyblok datasource entry; delete a Storyblok datasource entry; delete a Storyblok asset (pages using it lose the file). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.