Can I use Strapi as a CLI?

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

Can I expose Strapi through MCP?

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

Where are Strapi credentials stored?

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

Can I deny write access for Strapi MCP tools?

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

other

Strapi MCP Integration for Vercel AI SDK

Connect Strapi to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 4 read 3 write API token auth

Submit Strapi feedback View package source

Connect Strapi to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Strapi MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

{
  "mcpServers": {
    "kosmokrator-strapi": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=strapi",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=strapi --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Strapi instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Strapi Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Strapi integration catalog.

MCP tool	Source function	Type	Description
`integration__strapi__strapi_list_entries`	`strapi.strapi_list_entries`	Read	List entries for a content type in Strapi. Supports pagination, sorting, and field population (relations, media, components).
`integration__strapi__strapi_get_entry`	`strapi.strapi_get_entry`	Read	Get a single entry from Strapi by content type and ID. Supports population of relations and media.
`integration__strapi__strapi_create_entry`	`strapi.strapi_create_entry`	Write	Create a new entry in Strapi for a given content type. The data is automatically wrapped in the required "data" envelope.
`integration__strapi__strapi_update_entry`	`strapi.strapi_update_entry`	Write	Update an existing entry in Strapi by content type and ID. The data is automatically wrapped in the required "data" envelope.
`integration__strapi__strapi_delete_entry`	`strapi.strapi_delete_entry`	Write	Delete an entry from Strapi by content type and ID. This action is permanent.
`integration__strapi__strapi_list_content_types`	`strapi.strapi_list_content_types`	Read	List all content types defined in the Strapi Content-Type Builder. Returns API IDs, display names, and schema information.
`integration__strapi__strapi_get_current_user`	`strapi.strapi_get_current_user`	Read	Get the currently authenticated Strapi user. Useful for verifying the API token and checking permissions.

Related Strapi Pages

Strapi CLIUse direct JSON commands instead of MCP discovery. Strapi MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.