fetch_storiesLABSCO SUMMARY
Version history and rollback, not just create and publish.
Most CMS connectors stop at writing content. Having get_story_versions and restore_story in the same tool set is what makes it reasonable to let an assistant edit a live space — a bad update is one call to undo. Releases are the other piece worth knowing about: scheduled batches mean a set of changes can be prepared and go live together rather than trickling out.
What it is
A Storyblok management server. It wraps the Management API so an assistant can create and publish content, organise it, and handle the release and webhook plumbing around it.
What you get
- Stories:
fetch_storieswith filtering, pagination and search, plusget_story,create_story,update_storyanddelete_story - Publishing:
publish_storytakes it live andunpublish_storypulls it back - History:
get_story_versionslists previous versions andrestore_storyrolls one back;import_storybrings a story in with an optional language code - Tags:
fetch_tags,create_tag,delete_tag, andcreate_tag_and_add_to_storyin one step - Webhooks:
fetch_webhooks,get_webhook,create_webhook,update_webhook,delete_webhook - Releases:
fetch_releases,create_releaseandupdate_releasefor scheduled batches of content
Requirements
Clone it, build it, and point your client at build/index.js. It needs STORYBLOK_SPACE_ID, STORYBLOK_MANAGEMENT_TOKEN and STORYBLOK_DEFAULT_PUBLIC_TOKEN, plus GOOGLE_GENERATIVE_AI_API_KEY for the AI-assisted parts.
Setup effort
Build from source — git clone https://github.com/ArjunCodess/storyblok-mcp.git
USE CASES
01
Publishing a page from a draft in the conversation
Create the story, then take it live once you have read it back.
02
Undoing a change that went wrong
List the previous versions and restore the one that was right.
03
Organising content that grew messy
Find stories by search, then tag them — creating the tag and applying it in a single call.
04
Scheduling a batch of changes
Group content into a release so it goes live together instead of one page at a time.
116 tools
Listed in project docs. Your client may show a different list.
get_storycreate_storyupdate_storydelete_storypublish_storyunpublish_storyget_story_versionsrestore_storyimport_storyfetch_tagscreate_tagcreate_tag_and_add_to_storydelete_tagfetch_webhooksget_webhookcreate_webhookupdate_webhookdelete_webhookfetch_releasescreate_releaseupdate_releaseadd_story_to_releasepublish_releasedelete_releasefetch_presetsget_presetcreate_presetupdate_presetdelete_presetfetch_story_schedulingsget_story_schedulingcreate_story_schedulingupdate_story_schedulingdelete_story_schedulingfetch_access_tokensget_access_tokencreate_access_tokenupdate_access_tokendelete_access_tokenfetch_assetsget_assetdelete_assetinit_asset_uploadcomplete_asset_uploadfetch_asset_folderscreate_asset_folderupdate_asset_folderdelete_asset_folderfetch_componentsget_componentcreate_componentupdate_componentdelete_componentsearch_storiesget_story_by_slugfetch_foldersfetch_datasourcesget_datasourcecreate_datasourceupdate_datasourcedelete_datasourcefetch_datasource_entriesget_datasource_entrycreate_datasource_entryupdate_datasource_entrydelete_datasource_entrypingfetch_component_foldersget_component_foldercreate_component_folderupdate_component_folderdelete_component_folderfetch_space_rolesget_space_rolecreate_space_roleupdate_space_roledelete_space_rolefetch_spacesget_spacecreate_spaceupdate_spacedelete_spaceduplicate_spacebackup_spacegenerate_alt_texttranslate_storygenerate_meta_tagssummarize_storytag_story_with_aifetch_workflowsget_workflowcreate_workflowupdate_workflowduplicate_workflowdelete_workflowfetch_workflow_stagesget_workflow_stagecreate_workflow_stageupdate_workflow_stagedelete_workflow_stagefetch_workflow_stage_changesget_workflow_stage_changecreate_workflow_stage_changefetch_branchesget_branchcreate_branchupdate_branchdelete_branchdeploy_branchget_branch_storiescompare_branchescopy_stories_between_branchesfetch_branch_deploymentscreate_branch_deploymentget_branch_deploymentBEFORE YOU INSTALL
What to know first
Tools you get
116 tools named in the project's documentation.
Requires
- Node.js
- pnpm
- STORYBLOK_MANAGEMENT_TOKEN in your environment
- STORYBLOK_DEFAULT_PUBLIC_TOKEN in your environment
- GOOGLE_GENERATIVE_AI_API_KEY in your environment
- STORYBLOK_SPACE_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/ArjunCodess/storyblok-mcp.git
cd storyblok-mcp
pnpm install
pnpm run buildMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"storyblok": {
"command": "node",
"args": [
"<YOUR_PATH_TO_STORYBLOK_MCP>/build/index.js"
],
"env": {
"STORYBLOK_SPACE_ID": "<YOUR_STORYBLOK_SPACE_ID>",
"STORYBLOK_MANAGEMENT_TOKEN": "<YOUR_STORYBLOK_MANAGEMENT_TOKEN>",
"STORYBLOK_DEFAULT_PUBLIC_TOKEN": "<YOUR_STORYBLOK_DEFAULT_PUBLIC_TOKEN>",
"GOOGLE_GENERATIVE_AI_API_KEY": "<YOUR_GOOGLE_GENERATIVE_AI_API_KEY>"
}
}
}
}In Cursor, open Settings > MCP Tools > New MCP Server and paste this. <YOUR_PATH_TO_STORYBLOK_MCP>/build/index.js is the full path of build/index.js in your clone (right-click the file in Cursor and choose Copy Path).
