Connect Cursor to Vamo

Cursor connects to Vamo with a setup code. The Vamo app writes one line, you paste it into Cursor's agent, and the agent sets itself up. Developers can also connect with an API key, or have the agent call the Vamo API directly.

The ways Cursor can connect

There are three.

A setup code. The Vamo app shows one line holding a single-use code. You paste the line into Cursor's agent. The agent trades the code for a key and configures itself. You never copy a key by hand.

The MCP server with an API key. You create a key in Vamo. Cursor sends it with each request to the Vamo MCP server.

The direct API. Cursor's agent calls the Vamo REST API with a key. This suits code you are writing, more than questions you ask in chat.

Which one we recommend

Use the setup code. It is what the Pick your tool section offers for Cursor, and it suits most people. That section lets you choose a permission preset before it writes the line.

Choose the key route when you want to pick permissions one by one. Each key has its own permissions, chosen when you create it. Sign in or API key explains how keys work.

Choose the direct API when you are building something that uses Vamo. The first two routes let you ask for developers in plain language. The direct API lets your own code do the asking.

What you need

• A Vamo account on a Pro or Enterprise plan. API keys are on those plans.
• A role that can create keys: owner, admin or user. A read-only member cannot.
• For the key route or the direct API, a key from Set up > API keys. It is shown once.

A key can hold search, deep search, deep research, fit rank, lists and contacts. It cannot reach projects, outreach, members or billing.

Where to get the current steps

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

For the setup code, open the Set up > Get started at Set up > Get started and choose Cursor. It writes the line to paste. The code lasts ten minutes and works once, so paste it soon after you copy it.

For the key route, hand Cursor's agent the agent setup page. It tells the agent how to connect itself.

For the direct API, the API reference has every operation and its parameters. The open specification on api.vamotalent.ai needs no key. Give a coding agent the Vamo API covers what to hand the agent.

What a first good result looks like

For the setup code or the key route, start a new chat with Cursor's agent 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. Check that Vamo is connected has a longer check to paste in.

For the direct API, ask the agent to check the key. Vamo answers with the account, the key's label, the plan and the key's permissions. That check works with any key.

What commonly goes wrong

• The setup code is refused. It has expired, was already used, or a newer code replaced it. Get a new one from that section. See My setup code didn't work.
• Vamo is added but will not connect. The key may be wrong or revoked. See Vamo won't connect.
• The agent answers without using Vamo. Name Vamo in your request. See My assistant isn't using Vamo.
• The agent cannot read your usage or billing. The MCP server does not carry account, usage or billing information. Open Usage page in the app.

If something is not working