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 CLI for AI Agents

Use the Vero CLI from KosmoKrator to call Vero tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

6 functions 5 read 1 write API token auth

Submit Vero feedback View package source

Vero CLI Setup

Vero can be configured headlessly with `kosmokrator integrations:configure vero`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure vero --set auth_token="$VERO_AUTH_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor vero --json
kosmokrator integrations:status --json

Credentials

Authentication type: API token api_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`auth_token`	`VERO_AUTH_TOKEN`	Secret `secret`	yes	Auth Token
`url`	`VERO_URL`	URL `url`	no	API Base URL

Call Vero Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call vero.vero_get_current_user '{}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:vero vero_get_current_user '{}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs vero --json
kosmo integrations:docs vero.vero_get_current_user --json
kosmo integrations:schema vero.vero_get_current_user --json
kosmo integrations:search "Vero" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Vero.

`vero.vero_get_current_user`

Read read

Get the profile of the currently authenticated Vero user. Useful for verifying API connectivity and checking account details.

Parameters: none

Generic CLI call

kosmo integrations:call vero.vero_get_current_user '{}' --json

Provider shortcut

kosmo integrations:vero vero_get_current_user '{}' --json

`vero.vero_identify_user`

Read 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.

Parameters: id, email, name, data

Generic CLI call

kosmo integrations:call vero.vero_identify_user '{"id":"example_id","email":"example_email","name":"example_name","data":"example_data"}' --json

Provider shortcut

kosmo integrations:vero vero_identify_user '{"id":"example_id","email":"example_email","name":"example_name","data":"example_data"}' --json

`vero.vero_resubscribe`

Read read

Resubscribe a previously unsubscribed user to Vero email campaigns. The user will start receiving emails again.

Parameters: id

Generic CLI call

kosmo integrations:call vero.vero_resubscribe '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:vero vero_resubscribe '{"id":"example_id"}' --json

`vero.vero_track_event`

Read 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.

Parameters: identity, event_name, data

Generic CLI call

kosmo integrations:call vero.vero_track_event '{"identity":"example_identity","event_name":"example_event_name","data":"example_data"}' --json

Provider shortcut

kosmo integrations:vero vero_track_event '{"identity":"example_identity","event_name":"example_event_name","data":"example_data"}' --json

`vero.vero_unsubscribe`

Read read

Unsubscribe a user from all Vero email campaigns. The user will no longer receive any email communication.

Parameters: id

Generic CLI call

kosmo integrations:call vero.vero_unsubscribe '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:vero vero_unsubscribe '{"id":"example_id"}' --json

`vero.vero_update_user`

Write write

Update a user's profile in Vero. Pass the user ID, an optional new email, and a data object with attributes to update.

Parameters: id, email, data

Generic CLI call

kosmo integrations:call vero.vero_update_user '{"id":"example_id","email":"example_email","data":"example_data"}' --json

Provider shortcut

kosmo integrations:vero vero_update_user '{"id":"example_id","email":"example_email","data":"example_data"}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`vero.vero_get_current_user`

Get the profile of the currently authenticated Vero user. Useful for verifying API connectivity and checking account details.

Operation: Read read
Schema command: kosmo integrations:schema vero.vero_get_current_user --json

Parameter	Type	Required	Description
No parameters.

`vero.vero_identify_user`

Operation: Read read
Schema command: kosmo integrations:schema vero.vero_identify_user --json

Parameter	Type	Required	Description
`id`	string	yes	Unique user identifier (e.g., database ID or UUID).
`email`	string	yes	User email address.
`name`	string	no	Display name for the user.
`data`	object	no	Custom user attributes as key-value pairs (e.g., {"plan": "premium", "signup_date": "2025-01-15"}).

`vero.vero_resubscribe`

Resubscribe a previously unsubscribed user to Vero email campaigns. The user will start receiving emails again.

Operation: Read read
Schema command: kosmo integrations:schema vero.vero_resubscribe --json

Parameter	Type	Required	Description
`id`	string	yes	Unique user identifier to resubscribe.

`vero.vero_track_event`

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.

Operation: Read read
Schema command: kosmo integrations:schema vero.vero_track_event --json

Parameter	Type	Required	Description
`identity`	string	yes	User ID or email address identifying the user.
`event_name`	string	yes	Name of the event to track (e.g., "Logged in", "Added to cart", "Purchased").
`data`	object	no	Event-specific data as key-value pairs (e.g., {"product": "Widget", "price": 29.99}).

`vero.vero_unsubscribe`

Unsubscribe a user from all Vero email campaigns. The user will no longer receive any email communication.

Operation: Read read
Schema command: kosmo integrations:schema vero.vero_unsubscribe --json

Parameter	Type	Required	Description
`id`	string	yes	Unique user identifier to unsubscribe.

`vero.vero_update_user`

Update a user's profile in Vero. Pass the user ID, an optional new email, and a data object with attributes to update.

Operation: Write write
Schema command: kosmo integrations:schema vero.vero_update_user --json

Parameter	Type	Required	Description
`id`	string	yes	Unique user identifier to update.
`email`	string	no	New email address for the user.
`data`	object	no	Attributes to update as key-value pairs (e.g., {"plan": "enterprise", "company": "Acme Inc"}).

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.