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 MCP, CLI, and Lua Integration for AI Agents

Storyblok integration docs for AI agents: MCP gateway setup, Storyblok CLI commands, Lua API reference, credentials, and function schemas.

Storyblok for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Storyblok CLIHeadless setup, JSON output, direct function calls. Storyblok MCPExpose selected tools to local MCP clients. Storyblok LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: storyblok
route_slug: storyblok
package: storyblok
auth_strategy: bearer_token
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

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