Connect Claude to Vamo

Claude on the web and Claude Desktop connect to Vamo by browser sign-in. You add Vamo as a connector, Claude opens a Vamo page, and you approve. No API key is handled. Claude Desktop can also connect with an API key.

The ways Claude can connect

There are three.

Sign in with your browser. Claude opens a Vamo page. You approve, and Claude is connected. This works in Claude on the web and in Claude Desktop.

A connector with an API key. Claude Desktop sends a Vamo API key with each request. Claude on the web connects by sign-in only.

Skills with an API key. Skills are instructions Claude reads. They call the Vamo API directly with your key. They do not use the connector.

Which one we recommend

Sign in. It suits most people, and anyone who would rather not handle a key. A signed-in tool gets the search and enrich permissions by default. You can choose another preset on the sign-in page.

Choose a key in Claude Desktop when you want to pick permissions one by one. Each key has its own permissions, chosen when you create it.

Add skills when you want Claude to follow Vamo's own search methods. Skills and a connector can sit side by side. Sign in or API key compares the two in more detail.

What you need

• A Vamo account on a Pro or Enterprise plan. Approving a sign-in and creating a key both need one.
• A role that can create keys: owner, admin or user. A read-only member cannot approve a sign-in.
• For the key route or for skills, a key from Set up > API keys. It is shown once.
• For skills, Claude's sandbox must be allowed to reach api.vamotalent.ai. See below.

Where to get the current steps

The steps change as Claude changes, so they live in one place that is kept current.

Open the Set up > Get started at Set up > Get started and choose Claude Desktop. It gives you the address to add as a connector. The same address works in Claude on the web. Your browser then opens for you to sign in.

For the key route in Claude Desktop, the same card can give you a setup code instead. Or hand your agent the agent setup page. For skills, follow the skills install page.

Skills need the sandbox allowed

Claude runs skills in a sandbox. Vamo skills need that sandbox allowed to reach api.vamotalent.ai.

On a personal plan you can change this yourself. On a Team or Enterprise workspace only an org owner can. Claude Team and Enterprise admins covers what to ask them for.

A Vamo connector is not subject to that setting. If skills are blocked, the connector can still work.

What a first good result looks like

Start a new conversation and ask for people. For example:

Use Vamo to find the strongest engineers at <company>.

A good answer names real developers, says what each has built, and says why they fit. Claude then appears under Connected tools at Set up > API keys, with who approved it.

What commonly goes wrong

• You cannot add Vamo as a connector. Your company may not let you add custom connectors. See Can't add Vamo.
• The Vamo page will not let you approve. Your plan or role may not include it. See Sign-in fails or plan not included.
• Skills say the network is blocked. The sandbox cannot reach the Vamo API host. See the section above.
• Claude asks you to sign in again. A signed-in tool must sign in again after 90 days without use.

If something is not working