Storyblok
for LuumenAI
Read Storyblok content, links, and datasources from the terminal
Connect Storyblok with an API key and ask about the content behind a page. Pull a single story with STORYBLOK_GET_PAGE_ITEM, list items for any content type, resolve navigation with STORYBLOK_RETRIEVE_LINKS_GRAPHQL, or check datasource entries and tags. Read-only access, answered as you ask.
The Storyblok toolbox
10 tools, all read-only. They answer instantly, and every call is logged.
- ReadFetch Content Type Items (GraphQL)Fetch multiple stories/content items using Storyblok's GraphQL API with filtering and pagination.
- ReadFetch GraphQL Content ItemFetch a single story in a specific language using Storyblok GraphQL API with field-level translations.
- ReadGet Extension/AppRetrieve a Storyblok extension/app by ID using the Management API.
- ReadGet Datasource EntriesRetrieve datasource entries from Storyblok via GraphQL API.
- ReadGet GraphQL Rate LimitRetrieve rate limit information from Storyblok GraphQL API.
- ReadGet Page ItemRetrieve a single page item by ID or slug from Storyblok using GraphQL.
- ReadList GraphQL Content Type ItemsRetrieve multiple content items with pagination, filtering, and relation resolution for any Storyblok content type via GraphQL.
- ReadQuery page items via GraphQLExecute GraphQL queries to retrieve multiple page items from Storyblok with filtering options.
- ReadRetrieve Links via GraphQLRetrieve links for navigation using Storyblok's GraphQL API.
- ReadRetrieve Tags via GraphQLRetrieve tags from Storyblok via GraphQL API.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
No. Every one of the 10 tools LuumenAI has for Storyblok is read-only, so it can answer questions from Storyblok but cannot change anything in it. Read actions still follow the configured access and approval policy, and are recorded on the audit trail.
You decide. Access is granted per agent, skill, and team, and per environment — production is not staging.
Every call to Storyblok is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Storyblok to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.