Connect an AI agent to Storyblok
Choose a suitable Storyblok connection for the job at hand. Work with the project's actual tools, account and space, and send credentials only to their intended service.
To connect an AI agent to Storyblok, decide whether this is an editorial lookup or a change that belongs in a code review. A writer locating a draft and a developer preparing a schema migration can be working in the same space while needing different tools.
The storyblok-use-storyblok skill checks the available MCP session, CLI and project settings, then routes the task. It distinguishes a delivery token from a personal management token and uses only a credential source the operator has identified. When the project provides no reliable space ID, the intended target must be supplied.
What it does
- Identify the target space from relevant project settings or an explicit instruction.
- Choose the CLI for a change that needs a local diff and review.
- Check the active MCP toolset before relying on a remote operation.
- Use a delivery token for the appropriate content-reading path.
- Give the agent a credential reference for management work without pasting the secret into a conversation.
Install and use
- Install the official Storyblok skills and provide the project or target space. Configure an authorised CLI or MCP connection as appropriate.
- Ask, “Choose a route for a schema change that the team can review in version control.”
- Confirm the target and credential scope before proceeding. Keep personal management tokens out of browser code and chat.
FAQ
Source
Made by Storyblok. Original skill: storyblok-use-storyblok, published on GitHub under the MIT licence.
View on GitHub