MCP
Connect Claude, Cursor, or Codex to your Vergio account so your AI tools can query it directly.
MCP lets an AI assistant like Claude call Vergio as a set of tools. Your agent can search accounts with their evidence, work with pipeline data, record outcomes, and read supported watch, wallet, and supervision state without leaving the assistant. The reference labels tools as Live, Pilot, Activation-gated, or Unavailable from the capability manifest. Unavailable tools remain published for compatibility and are not callable in the current wallet-live product state.
Connect Claude (recommended)
In Claude (Desktop, web, or Claude Code), open Settings > Connectors, choose Add custom connector,
and paste the endpoint https://vergio.ai/api/mcp. Claude sends you to Vergio to sign in and approve
access, then Vergio's tools appear in Claude. No key to create or manage, and you can revoke access any
time by removing the connector.
Connect with an API key
For Cursor, Codex, scripts, or programmatic use, create a key under
Integrations > API & MCP > Create key and point your client at https://vergio.ai/api/mcp with
the key as a Bearer header. The self-serve screen currently offers Read access, Write outcomes, and
Generate reports; Read access also grants read:watch. Other protocol scopes shown in the reference
are not selectable for a new self-serve key. For example, in Claude Code:
claude mcp add --transport http vergio https://vergio.ai/api/mcp \
--header "Authorization: Bearer vg_live_your_key_here"The full setup for Claude Code, Claude Desktop, Cursor, and Codex, plus the reference for every tool, is in the MCP reference.
Claude connector OAuth is different from a self-serve key: Vergio derives its scopes from the signed-in member's workspace role. Outreach tools still require approved pilot access, and wallet or supervision tools can also require role or funding state.
Related
Updated July 28, 2026