Productivity & Project Management · Storyblok + Claude
Storyblok MCP with Claude: Update and Publish Website Content Through Plain-Language Requests
The short answer
Claude works with Storyblok through the Model Context Protocol (MCP), an open standard that acts as a secure adapter. Once connected, Claude can read content, create entries, update fields, fetch assets and prepare publishing, using the sign-in method and permissions your organisation chooses. People approve consequential changes before they go live.
What is Storyblok?
Storyblok is a headless content management system with a visual editor. It stores content separately from the places it appears, so one piece of content can be delivered to websites, apps and other digital channels. Marketing teams, content editors, product teams and digital agencies typically use it to keep messaging consistent across many platforms while giving editors a familiar visual way to work.
How Claude connects to Storyblok through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software. In plain terms, it is a universal adapter between Claude and a tool like Storyblok. Storyblok supports connection through an MCP server or a direct API, and sign-in can use an API key or OAuth sign-in, depending on what suits your setup.
Once connected, Claude can work with the content inside Storyblok. For example, it can create new entries from a brief, update existing text, look up assets, and prepare changes for publishing. Claude can also help teams find and tidy content across a large space, saving hours of manual searching.
Permissions and approvals keep people in charge. Access is limited to the spaces and actions your organisation allows, following least-privilege principles. Publishing and other consequential actions can require a named person to review and approve first, and activity is logged so you can see what was changed and when.
What you can automate
Drafting new landing pages
A marketing manager describes a campaign in a few sentences. Claude creates the page entries in Storyblok with headings, body copy and image references, following the structure the team already uses. The editor reviews the draft in the visual editor before anything goes live.
Updating product information across pages
When a product price, name or specification changes, a content operations lead can ask Claude to find every entry that mentions it. Claude lists the matches and proposes updates. The team confirms the changes, which saves the manual hunt across many pages.
Organising the asset library
Digital teams often accumulate thousands of images and files. Claude can fetch assets by name, tag or folder, suggest missing alt text and help locate the right image for a page, so designers spend less time searching.
Preparing localised content
A regional team can ask Claude to create translated drafts of existing entries for review. Native speakers check the wording and tone before publishing, which speeds up launches in several markets without skipping quality checks.
Auditing content quality
A digital operations manager can ask Claude to review entries for missing fields, broken asset references or outdated dates. Claude produces a clear list of issues, and the team decides what to fix, helping keep the site accurate over time.
An end-to-end workflow: Campaign launch from a brief to a reviewed draft
TriggerA marketing lead adds a campaign brief to a shared document in Microsoft 365 and marks it ready for drafting.
Claude reads the brief from the shared document and summarises the key messages and audience.
Claude creates draft entries in Storyblok for the landing page, banner and email hero section, using existing components.
Claude fetches approved product images from the asset library and attaches them to the matching entries.
Claude logs the draft entries and their links in the team's project tracker in Microsoft 365 for review.
The content editor reviews each draft in the visual editor and approves the entries for publishing.
A named approver publishes the approved entries, and the audit log records each action.
OutcomeCampaign pages are drafted in hours rather than days, with clear human review before publication. Typical results vary by team size, content volume and approval steps.
How we set it up
Free automation audit
We review how your teams create, approve and publish content in Storyblok, and identify the workflows worth automating first.
Secure connection
We connect Claude to your Storyblok space using an API key or OAuth sign-in, whichever suits your security policy, with least-privilege access.
Workflow design
We design the end-to-end process across Storyblok and your other systems, such as Microsoft 365, CRM or ticketing, with approval points for publishing.
Testing against real content
We test the workflow using past briefs and existing entries to check accuracy, tone and structure before anything reaches your live site.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your editors, marketers and approvers on how to work alongside Claude.
Who benefits
- Marketing managers
- Faster drafting of campaign pages and messaging, with consistent structure across channels.
- Content editors
- Less time on repetitive entry creation and updates, leaving more time for quality and voice.
- Digital operations leads
- Clear audit trails, quality checks and a single process for changes across the content library.
- IT and security heads
- Controlled, least-privilege access with approvals, so automation stays within policy.
Security and control
- Least-privilege access limits Claude to the spaces and actions your organisation approves.
- Named human approval is required before consequential actions such as publishing.
- Audit logs record what was created, changed or published, and by whom.
- Test environments and draft-only modes let teams try workflows before they touch live content.
- Credentials are managed under your control, and access can be revoked at any time.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the Claude workflow in their chosen region to align with their data protection requirements. Indian organisations can design workflows that support obligations under the Digital Personal Data Protection Act, 2023. Organisations in the UAE and Saudi Arabia can meet local data protection laws through regional hosting choices. We select the hosting region with you during the audit so it meets your requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Storyblok MCP server do?
The Storyblok MCP server lets an AI assistant such as Claude read and work with content in your Storyblok space through a secure, standard connection. Typical actions include creating entries, updating content, fetching assets and preparing changes for publishing, all within the access you grant.
Is connecting Storyblok to Claude secure?
Security depends on how the connection is set up. We use the sign-in method Storyblok supports, such as an API key or OAuth sign-in, and apply least-privilege access so Claude only reaches what it needs. Approvals and audit logs add further control over changes.
What can Claude do with Storyblok once connected?
Typically, Claude can draft new entries from a brief, update existing fields, search and fetch assets, check content for issues and help prepare publishing. Consequential actions can require a person to approve before they take effect.
How long does setup take?
Timelines vary with the size of your space and the workflows involved. A focused project often takes a few weeks from the free audit to launch, including testing and team training. We confirm a realistic timeline during the audit.
What plan or permissions do I need?
You need a Storyblok space with access that allows the sign-in method you choose, typically an API key or OAuth authorisation by a user with suitable rights. Requirements depend on your existing setup, and we confirm the exact permissions during the free audit.