Connect another AI tool or your own agent to Vamo

Any AI tool or agent can use Vamo if it can do one of two things. It can connect to a remote MCP server, with browser sign-in or a header you set. Or it can make HTTP calls with an API key. Choose Other in the Pick your tool section to get the current steps.

What your tool needs

Check your tool against this list. One match is enough.

• It connects to remote MCP servers and supports sign-in. The tool opens a Vamo page and you approve. No key is handled.
• It connects to remote MCP servers and lets you set a header. The tool sends a Vamo API key with each request.
• It can make HTTP calls. The agent reads the Vamo skills, or calls the Vamo API directly, with a key.

The ways it can connect

Setup code. The Pick your tool section gives you one line to paste into your agent. The line holds a single-use code. Your agent trades the code for a key and configures itself.

Sign in with your browser. A tool on your own machine can sign in this way, if it supports sign-in for MCP servers.

MCP with an API key. This works in every tool that lets you set a header.

Skills with an API key. Skills are instructions an agent reads. They call the Vamo API over HTTP. They do not use MCP.

The API directly. A developer or coding agent calls the Vamo API with a key.

Which one we recommend

Start with the setup code if your agent can follow a pasted instruction. You handle no key yourself.

Choose MCP with a key when your tool has a place to add a server and a header. You pick the key's permissions when you create it.

Choose skills or the API for an agent you built yourself, or one with no MCP support. MCP, skills and the API explains how the three differ. Give a coding agent the Vamo API covers the direct route.

What you need

• A Vamo account on a Pro or Enterprise plan. Creating a key and approving a sign-in both need one.
• A role that can create keys: owner, admin or user. A read-only member cannot.
• For any key route, a key from Set up > API keys. It is shown once.
• A network that lets your tool reach mcp.vamotalent.ai for MCP, or api.vamotalent.ai for skills and the API.

Where to get the current steps

• Open the Set up > Get started at Set up > Get started and choose Other. It writes the current line for you.
• The agent setup page has prompts an agent can follow to set itself up.
• The skills catalog lists every skill. The skills install page covers installing them.
• The API reference has the API reference and guides.

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.

Then open Set up > API keys. A key shows when it was last used. A tool that signed in appears under Connected tools, with who approved it.

What commonly goes wrong

• The setup code is refused. A code is single use and lasts ten minutes. Get a fresh one from that section. See Setup code didn't work.
• The tool has nowhere to set a header. MCP with a key will not work there. Use the setup code, skills or the API.
• The tool cannot reach Vamo. A company network or a sandbox may block it. See Vamo won't connect.
• The agent asks for something a key cannot do. A key or signed-in tool can hold search, deep search, deep research, fit rank, lists and contacts. Projects, outreach, members and billing stay in the Vamo app.

If something is not working