# How to connect Storyblok to OpenClaw (paste one key, 10 tools) > Connect Storyblok to OpenClaw with ClawLink: paste your Storyblok key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/storyblok The usual route to Storyblok access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Storyblok setup: install one ClawHub skill, connect Storyblok in the browser, and OpenClaw can call real Storyblok actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/storyblok ## Setup It takes three steps to connect OpenClaw to Storyblok. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Storyblok** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect storyblok # connect Storyblok (browser OAuth) npx -y @useclawlink/cli actions storyblok # list available actions npx -y @useclawlink/cli run storyblok --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Storyblok in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Storyblok API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Storyblok, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Storyblok is connected in the dashboard, that agent calls the same 10 Storyblok tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Storyblok MCP for OpenClaw Looking for a Storyblok MCP server for OpenClaw? ClawLink connects Storyblok to OpenClaw and exposes 10 Storyblok tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Storyblok integration](https://claw-link.dev/hermes/storyblok) works the same way. ## What the OpenClaw Storyblok integration can do 10 Storyblok tools are ready for OpenClaw once the account is connected. ### All 10 Storyblok tools for OpenClaw | Tool | What it does | |---|---| | **Fetch content type items graphql** `storyblok_fetch_content_type_items_graphql` | Fetch multiple stories/content items with filtering and pagination | | **Fetch graphql content item** `storyblok_fetch_graphql_content_item` | Fetch a single story by ID or slug with optional language translation | | **Get app** `storyblok_get_app` | Retrieve a Storyblok extension or app by ID | | **Get datasource entries** `storyblok_get_datasource_entries` | Retrieve datasource entries (id, name, value) | | **Get graphql rate limit** `storyblok_get_graphql_rate_limit` | Check the GraphQL API rate limit and max cost per request | | **Get page item** `storyblok_get_page_item` | Get a single page item by ID or slug in draft or published version | | **List graphql content type items** `storyblok_list_graphql_content_type_items` | List content items for a content type with pagination and filtering | | **Query page items** `storyblok_query_page_items` | Query multiple page items with filters like path prefix or slug exclusions | | **Retrieve links graphql** `storyblok_retrieve_links_graphql` | Retrieve navigation links with slug, name, and published status | | **Retrieve tags** `storyblok_retrieve_tags` | Retrieve tags used for content organization and filtering | ## Example prompts **Fetch Content Type Items Graphql** > Pull the relevant data from Storyblok, summarize it in plain English, and point out anything that needs attention. **Fetch Graphql Content Item** > Pull the relevant data from Storyblok, summarize it in plain English, and point out anything that needs attention. **Get App** > Pull the relevant data from Storyblok, summarize it in plain English, and point out anything that needs attention. **Get Datasource Entries** > Pull the relevant data from Storyblok, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Storyblok working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Storyblok API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Storyblok account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Storyblok. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Storyblok actions to the runtime in a format your agent can reliably use. | 10 tools for Storyblok are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Storyblok to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Storyblok in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Storyblok key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Storyblok skill but can't call the tools The ClawHub skill teaches OpenClaw about Storyblok, but the calls run through the ClawLink plugin and your connected account. Make sure Storyblok is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Storyblok from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Storyblok tools Storyblok tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Storyblok call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Storyblok returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Storyblok has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Storyblok integration? Yes. ClawLink is the fastest way to connect OpenClaw to Storyblok: link your Storyblok account once in the browser and OpenClaw can call the Storyblok API through 10 ready-made tools — no custom code or token handling. ### How do I add Storyblok to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Storyblok skill from ClawHub, then you click Connect in the dashboard to authorize Storyblok. OpenClaw calls the tools from the next message — no config files, and the Storyblok key you paste is stored server-side instead of in your environment. ### How long does it take to connect Storyblok to OpenClaw? About two minutes. Sign in, click Connect next to Storyblok in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Storyblok up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Storyblok working from chat. ### OpenClaw installed the Storyblok skill but can't call the tools The ClawHub skill teaches OpenClaw about Storyblok, but the calls run through the ClawLink plugin and your connected account. Make sure Storyblok is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.