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.

productivity

Vero MCP, CLI, and Lua Integration for AI Agents

Vero integration docs for AI agents: MCP gateway setup, Vero CLI commands, Lua API reference, credentials, and function schemas.

Vero for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Vero CLIHeadless setup, JSON output, direct function calls. Vero MCPExpose selected tools to local MCP clients. Vero LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: vero
route_slug: vero
package: vero
auth_strategy: api_token
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Parameters	Description
`vero.vero_get_current_user`	Read `read`	0	Return Vero Track API configuration status. Vero does not expose a current-user endpoint, so API access is verified when write tools run.
`vero.vero_identify_user`	Write `write`	5	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_update_user`	Write `write`	3	Update a user's profile in Vero via the official identify endpoint. Pass the user ID, an optional email, and a data object with attributes to update.
`vero.vero_alias_user`	Write `write`	2	Change a Vero user identifier with the official alias endpoint. This merges identities and should be used carefully.
`vero.vero_unsubscribe`	Write `write`	1	Unsubscribe a user from all Vero email campaigns. The user will no longer receive any email communication.
`vero.vero_resubscribe`	Write `write`	1	Resubscribe a previously unsubscribed user to Vero email campaigns. The user will start receiving emails again.
`vero.vero_delete_user`	Write `write`	1	Delete a Vero user by ID. This permanently removes profile properties and tracked activity.
`vero.vero_edit_tags`	Write `write`	3	Add and/or remove tags on a Vero user profile using the official tag edit endpoint.
`vero.vero_track_event`	Write `write`	4	Track a behavioral event for a user in Vero. Pass an identity object with id and/or email, an event name, optional event data, and optional extras such as source or created_at.
`vero.vero_api_get`	Read `read`	2	Call a relative Vero API GET path. Use for documented endpoints not yet exposed as first-class tools.
`vero.vero_api_post`	Write `write`	2	Call a relative Vero API POST path. Use for documented endpoints not yet exposed as first-class tools.
`vero.vero_api_put`	Write `write`	2	Call a relative Vero API PUT path. Use for documented endpoints not yet exposed as first-class tools.
`vero.vero_api_delete`	Write `write`	2	Call a relative Vero API DELETE path. Use for documented endpoints not yet exposed as first-class tools.