Vero MCP Integration for Claude Code
Connect Vero to Claude Code through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.
Connect Vero to Claude Code
Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry.
Add KosmoKrator as a stdio MCP server in the Claude Code project config and select the integrations that should be visible. The gateway is local, scoped to this integration, and starts with
--write=deny so Claude Code can inspect read-capable tools without receiving write access by default.
Vero MCP Config for Claude Code
Claude Code can launch the local kosmo binary directly from the project MCP config.
{
"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
Expose only Vero instead of a broad multi-service tool list.
Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.
Start read-only, then opt into ask or allow for trusted workspaces.
Vero Tools Visible to Claude Code
Claude Code 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. |