Can I use Clerk as a CLI?

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

Can I expose Clerk through MCP?

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

Where are Clerk credentials stored?

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

Can I deny write access for Clerk MCP tools?

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

other

Clerk MCP Integration for Vercel AI SDK

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

7 functions 4 read 3 write API key auth

Submit Clerk feedback View package source

Connect Clerk 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.

Clerk MCP Config for Vercel AI SDK

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Clerk 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.

Clerk Tools Visible to Vercel AI SDK

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

MCP tool	Source function	Type	Description
`integration__clerk__clerk_list_users`	`clerk.clerk_list_users`	Read	List users from Clerk with optional filtering and pagination. Returns user IDs, emails, names, and profile details.
`integration__clerk__clerk_get_user`	`clerk.clerk_get_user`	Read	Retrieve a single Clerk user by their user ID. Returns full profile details including email, name, and metadata.
`integration__clerk__clerk_create_user`	`clerk.clerk_create_user`	Write	Create a new user in Clerk. Requires at least one email address. Optionally set name, password, and username.
`integration__clerk__clerk_update_user`	`clerk.clerk_update_user`	Write	Update an existing Clerk user's profile. Provide the user ID and fields to update.
`integration__clerk__clerk_delete_user`	`clerk.clerk_delete_user`	Write	Delete a user from Clerk. This action is irreversible and will remove all associated data.
`integration__clerk__clerk_list_organizations`	`clerk.clerk_list_organizations`	Read	List organizations from Clerk with optional filtering and pagination. Returns organization IDs, names, and metadata.
`integration__clerk__clerk_get_current_user`	`clerk.clerk_get_current_user`	Read	Health check — verify Clerk API connectivity by fetching the first user. Returns a single user or empty result to confirm the API is reachable.

Related Clerk Pages

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