Can I use Vero as a CLI?

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

Can I expose Vero through MCP?

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

Where are Vero credentials stored?

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

Can I deny write access for Vero MCP tools?

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

Vero MCP Integration for Claude Agent SDK

Connect Vero to Claude Agent SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 5 read 1 write API token auth

Submit Vero feedback View package source

Connect Vero to Claude Agent SDK

Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server.

Add a KosmoKrator stdio MCP server to the Claude Agent SDK options. The gateway is local, scoped to this integration, and starts with --write=deny so Claude Agent SDK can inspect read-capable tools without receiving write access by default.

Vero MCP Config for Claude Agent SDK

Use a narrow integration list so the agent does not load unrelated tools.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Vero Tools Visible to Claude Agent SDK

Claude Agent SDK sees stable MCP tool names generated from the Vero integration catalog.

MCP tool	Source function	Type	Description
`integration__vero__vero_get_current_user`	`vero.vero_get_current_user`	Read	Get the profile of the currently authenticated Vero user. Useful for verifying API connectivity and checking account details.
`integration__vero__vero_identify_user`	`vero.vero_identify_user`	Read	Identify (create or update) a user in Vero. Pass a unique user ID, email, optional name, and any custom attributes in the data object. This creates the user if they don't exist, or updates their profile if they do.
`integration__vero__vero_resubscribe`	`vero.vero_resubscribe`	Read	Resubscribe a previously unsubscribed user to Vero email campaigns. The user will start receiving emails again.
`integration__vero__vero_track_event`	`vero.vero_track_event`	Read	Track a behavioral event for a user in Vero. Events can trigger automated email campaigns. Pass a user identity (ID or email), event name, and optional event data.
`integration__vero__vero_unsubscribe`	`vero.vero_unsubscribe`	Read	Unsubscribe a user from all Vero email campaigns. The user will no longer receive any email communication.
`integration__vero__vero_update_user`	`vero.vero_update_user`	Write	Update a user's profile in Vero. Pass the user ID, an optional new email, and a data object with attributes to update.

Related Vero Pages

Vero CLIUse direct JSON commands instead of MCP discovery. Vero MCPFull gateway reference and MCP tool names. KosmoKrator for Claude Agent SDKClient-level gateway setup.