Can I use Storyblok as a CLI?

Yes. KosmoKrator exposes a Storyblok CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Storyblok through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Storyblok tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Storyblok credentials stored?

Storyblok credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Storyblok MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

data

Storyblok CLI for Coding Agents

Use the Storyblok CLI for coding agents with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 4 read 3 write Bearer token auth

Submit Storyblok feedback View package source

Storyblok CLI for Coding Agents

Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

Use this pattern when another coding agent needs exact commands and schema discovery. The Storyblok CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Storyblok CLI for Coding Agents
kosmokrator integrations:configure storyblok --set access_token="$STORYBLOK_ACCESS_TOKEN" --set space_id="$STORYBLOK_SPACE_ID" --enable --read allow --write ask --json
kosmo integrations:call storyblok.storyblok_list_stories '{"page":1,"per_page":1,"search":"example_search","sort_by":"example_sort_by"}' --json

Discovery Before Execution

Agents and scripts can inspect Storyblok docs and schemas before choosing a function.

kosmo integrations:docs storyblok --json
kosmo integrations:docs storyblok.storyblok_list_stories --json
kosmo integrations:schema storyblok.storyblok_list_stories --json
kosmo integrations:search "Storyblok" --json
kosmo integrations:list --json

Useful Storyblok CLI Functions

Function	Type	Parameters	Description
`storyblok.storyblok_list_stories`	Read	page, per_page, search, sort_by	List stories in the configured Storyblok space. Supports pagination, search, and sorting.
`storyblok.storyblok_get_story`	Read	id	Retrieve a single Storyblok story by its numeric ID, including full content.
`storyblok.storyblok_create_story`	Write	name, slug, content, parent_id, is_startpage, tag_list	Create a new story in the configured Storyblok space. Requires a name, slug, and content object.
`storyblok.storyblok_update_story`	Write	id, content, name, slug, tag_list	Update an existing Storyblok story. Provide the story ID and the fields to update (e.g., content, name, slug).
`storyblok.storyblok_delete_story`	Write	id	Delete a story from the configured Storyblok space by its numeric ID. This action is irreversible.
`storyblok.storyblok_list_components`	Read	none	List all component schemas defined in the configured Storyblok space. Useful for understanding available content structures.
`storyblok.storyblok_get_current_user`	Read	none	List all available Storyblok spaces for the authenticated user. Useful as a health check or to discover space IDs.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Storyblok CLI Pages

CI Storyblok CLI for CI. Cron Jobs Storyblok CLI for cron jobs. Shell Scripts Storyblok CLI for shell scripts. Headless Automation Storyblok CLI for headless automation.