MCP

Connect your AI tools to Vergio so they can query your account directly: which of your accounts went in-market this week and why, and report the outcome when you win a deal. The same key works for the REST API and MCP.

What your agency gets

MCP (Model Context Protocol) lets an assistant like Claude call Vergio as a set of tools. Your agent can pull your weekly list with its evidence, search your scored accounts, read one account's signals, and record what happened after you reached out, without leaving the assistant.

Install

Pick your client. Each snippet uses the endpoint https://vergio.ai/api/mcp.

Run in your project. The Vergio tools appear in Claude Code's tool list.

claude mcp add --transport http vergio https://vergio.ai/api/mcp \
  --header "Authorization: Bearer vg_live_your_key_here"

Create the key in your workspace under Settings, then API keys, and paste it in place of the placeholder.

Tools

Your agent gets these 5 tools. Reading is available on any key; recording outcomes needs the write:outcomes scope.

list_in_market_accounts

This week's surfaced in-market accounts for your agency, each with the evidence (score reasoning + top signals) behind it. Call this to see who to reach out to now.

Input	Type	Required
`icp_profile`	string	no

search_accounts

Search your scored accounts. Filter by minimum In-Market score (0-100), tier, or status; results are cursor-paginated (pass the returned next_cursor to page).

Input	Type	Required
`min_score`	number	no
`tier`	string	no
`status`	string	no
`icp_profile`	string	no
`limit`	number	no
`cursor`	string	no

get_account_evidence

Full detail for one account: its In-Market / Fit / Intent / Opportunity scores, the plain-English reasoning, and its signal timeline. Pass the storeId from a list/search result.

Input	Type	Required
`store_id`	string	yes

get_account_signals

The signal history for one account (optionally since a date). Use it to understand what changed and when.

Input	Type	Required
`store_id`	string	yes
`since`	string	no

record_outcome

Report what happened after you reached out to an account. Call this when you know the result (contacted, replied, call_booked, proposal, won, lost) — it becomes a learning label that improves everyone's rankings. Requires the write:outcomes scope.

Input	Type	Required
`store_id`	string	yes
`action`	"contacted" \| "replied" \| "call_booked" \| "proposal" \| "won" \| "lost"	yes
`value`	number	no
`note`	string	no
`event_id`	string	no

Is this page helpful?