Can Lyro create or publish content in Storyblok?

No. Every action in this toolkit reads - Get Page Item, Retrieve Links via GraphQL, Get Datasource Entries and the rest all query the API rather than write to it. Authoring and publishing stay with your content team in the visual editor, and Lyro answers from whatever is live at the time.

Can Lyro read draft stories, or only published ones?

Get Page Item supports both draft and published versions, so an internal question can be answered from a draft while customer-facing replies stay on the published version. Which one Lyro sees depends on the version the query asks for and on the access token the connection was made with.

Will frequent lookups hit Storyblok's GraphQL rate limit?

Storyblok limits by query cost rather than call count, and Get GraphQL Rate Limit returns the maximum cost per request so the safe rate can be worked out as 100 divided by that cost. Because the GraphQL actions support field-level selection, Lyro can request only the fields an answer needs and keep the cost per call low.

Why does the toolkit include Get Extension/App when everything else is GraphQL?

It is the one action that goes through the Management API instead, retrieving an installed extension or app by ID. That is a different credential from the delivery token the GraphQL actions use, so it only works when the connection carries Management API access.

Storyblok MCP integration

Fetches published pages by slug, filters content type entries, and reads navigation links, tags, and datasource values through Storyblok's GraphQL API.

Connect Storyblok See all integrations

10actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Fetch graphql content item
Lyro retrieves a story in Storyblok with language-specific translations. Agents access localized content for customers in their language.
Fetch content type items (graphql)
Lyro pulls multiple content items from Storyblok with filtering and pagination. Agents retrieve product catalogs or help articles on demand.
List graphql content type items
Lyro retrieves multiple content items with pagination and relation resolution. Agents browse structured data without crafting complex queries.

See all 10 actions

How businesses use Storyblok + Lyro

Each card is one request a support team gets, and the Storyblok actions Lyro runs to close it.

Answer from the page that is actually published
Lyro retrieves a single page item by slug or ID and selects only the fields it needs, so a customer question is answered from the live Storyblok entry rather than a summary of it.
Get Page ItemFetch GraphQL Content ItemQuery Page Items via GraphQL
Serve the language version the customer is reading
Storyblok prefixes translated stories with a language code, so Lyro filters on that prefix to pull the Spanish or Hindi version of an entry and answers in the language the conversation is already in.
Fetch Content Type ItemsFetch GraphQL Content ItemList GraphQL Content Type Items
Point a customer at a link that exists and is live
Lyro reads the link tree with each entry's slug, name, and published status, checks the tags attached to it, and hands over a URL that resolves instead of one inferred from the topic.
Retrieve Links via GraphQLRetrieve Tags via GraphQLList GraphQL Content Type Items
Read the datasource values behind a list or form
Shipping tiers, country lists, and similar option sets live in Storyblok as datasource name and value pairs, and Lyro reads them directly so an answer matches exactly what the site renders.
Get Datasource EntriesFetch Content Type ItemsGet Page Item

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Storyblok actions it has and picks the ones a request needs.

01
Connect Storyblok
Authorize the Storyblok account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Storyblok actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Storyblok · Lyro

Everything else about Storyblok

Setup, permissions, and the limits of what Lyro can do inside Storyblok.

No. Every action in this toolkit reads - Get Page Item, Retrieve Links via GraphQL, Get Datasource Entries and the rest all query the API rather than write to it. Authoring and publishing stay with your content team in the visual editor, and Lyro answers from whatever is live at the time.

Every action available in Storyblok

All 10 actions your agent can call on Storyblok, straight from the live MCP connection.

Fetch content type items (graphql)
Fetch multiple stories/content items using Storyblok's GraphQL API with filtering and pagination.
Fetch graphql content item
Fetch a single story in a specific language using Storyblok GraphQL API with field-level translations.
Get extension/app
Retrieve a Storyblok extension/app by ID using the Management API.
Get datasource entries
Retrieve datasource entries from Storyblok via GraphQL API.
Get graphql rate limit
Retrieve rate limit information from Storyblok GraphQL API.
Get page item
Retrieve a single page item by ID or slug from Storyblok using GraphQL.
List graphql content type items
Retrieve multiple content items with pagination, filtering, and relation resolution for any Storyblok content type via GraphQL.
Query page items via graphql
Execute GraphQL queries to retrieve multiple page items from Storyblok with filtering options.
Retrieve links via graphql
Retrieve links for navigation using Storyblok's GraphQL API.
Retrieve tags via graphql
Retrieve tags from Storyblok via GraphQL API.