Connect Claude to Vergio by signing in, no API key needed

Somewhere in most agencies there is a config file, or a pinned Slack message, with an API key sitting in it. It was pasted once so the team's AI assistant could reach a tool, and it has stayed there ever since: never rotated, copied by whoever needed it next, handing the same full access to the new hire and the owner alike. Connecting Claude to Vergio used to start exactly this way. As of this week it does not.

In Claude Desktop, on the web, or in Claude Code, you now connect Claude to Vergio by signing in. Open Settings, then Connectors, choose Add custom connector, and paste the Vergio endpoint (https://vergio.ai/api/mcp). Claude sends you to Vergio to sign in and approve access, and Vergio's tools appear in the assistant. Nothing to create, nothing to copy, nothing to rotate. Remove the connector whenever you want and the access is gone.

Why a sign-in beats a pasted key

A shared key grants access by who is holding the string. A sign-in grants it by who is asking. For a team, that gap is the whole point.

A pasted key is one secret that behaves the same in every pair of hands. It cannot tell the account owner from a contractor you brought on last week, and it keeps working long after that contractor leaves, until someone remembers to rotate it. Signing in ties the connection to a person and their role instead. Access follows your Vergio workspace: every active member can read accounts and record outcomes, deals, contacts, and outreach, while managing webhooks stays with owners and admins. Take someone off the workspace, or have them remove the connector, and their access ends with it.

For a solo operator that difference is small. For an agency where three or four people touch the same pipeline, it is the line between a shared password and access you can actually reason about. When someone leaves, you do not have to remember which tools their key could reach and scramble to rotate it; you take them off the workspace and the connection dies with the seat. If you handed a key around the team to wire up Claude, the useful move this week is to delete it and have each person connect by signing in.

What your team can actually do with it

The reason to connect at all is simple: a Vergio question your team currently answers by hand is one the assistant can answer instead. We index 7M+ stores across Shopify and WooCommerce to map the market, and monitor a panel of 60,000+ of them closely enough to see what changes, a microscope on that map. Connected to Claude, that whole read is something your team can ask about in plain language.

Ask which of your monitored beauty prospects are missing a reviews app and a real figure comes back, scoped to your list, off the same 97% adoption read we broke down in the app-stack pulse. The answer is grounded in the data, not guessed, because Vergio's tools do the reading and the assistant only phrases it.

Pick the one Vergio question your team currently copies into a spreadsheet every Monday and ask Claude for it instead. That is the whole payoff, and it is available the moment you connect.

The honest scope

Two limits worth stating plainly. Signing in is a Claude feature: Cursor, Codex, and your own scripts still connect with a Vergio API key, which is also what the REST API uses, so keys are not going anywhere for programmatic work. And the sign-in grants exactly the access your role already has, it does not widen it. Nothing about how the tools behave changed. Only the way you connect got simpler.

We built the sign-in flow because every agency we onboarded hit the same wall first, and it was never the tools, it was the key: someone had to create one, decide where to store it, and hope it never leaked. Removing that step is a small thing that unblocks the actual work. The full setup and the reference for every tool live in the MCP docs, and the changelog entry has the short version. If you have not put Vergio in front of your team yet, start from the product and add the connector from there.