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 Headless Automation

Use the Vero CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

6 functions 5 read 1 write API token auth

Submit Vero feedback View package source

Vero CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Vero CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Vero CLI for Headless Automation
kosmokrator integrations:configure vero --set auth_token="$VERO_AUTH_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call vero.vero_get_current_user '{}' --json

Discovery Before Execution

Agents and scripts can inspect Vero docs and schemas 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

Useful Vero CLI Functions

Function	Type	Parameters	Description
`vero.vero_get_current_user`	Read	none	Get the profile of the currently authenticated Vero user. Useful for verifying API connectivity and checking account details.
`vero.vero_identify_user`	Read	id, email, name, data	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.
`vero.vero_resubscribe`	Read	id	Resubscribe a previously unsubscribed user to Vero email campaigns. The user will start receiving emails again.
`vero.vero_track_event`	Read	identity, event_name, data	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.
`vero.vero_unsubscribe`	Read	id	Unsubscribe a user from all Vero email campaigns. The user will no longer receive any email communication.
`vero.vero_update_user`	Write	id, email, data	Update a user's profile in Vero. Pass the user ID, an optional new email, and a data object with attributes to update.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Vero CLI Pages

CI Vero CLI for CI. Cron Jobs Vero CLI for cron jobs. Shell Scripts Vero CLI for shell scripts. Coding Agents Vero CLI for coding agents.