Connect ChatGPT to Vamo

ChatGPT connects to Vamo by browser sign-in. You add the Vamo MCP server in ChatGPT, a Vamo page opens, and you approve. No API key is handled. Where your workspace has skills turned on, you can add Vamo skills as well.

The ways ChatGPT can connect

There are two.

Sign in with your browser. You add the Vamo MCP server to ChatGPT. Your browser opens a Vamo page. You approve, and ChatGPT is connected.

Skills. Skills are instructions ChatGPT reads. Each one teaches a Vamo method, such as searching or building a list. Skills are switched on per workspace by its owners, so you may not have them.

Which one we recommend

Sign in. It suits most people, and it works whether or not your workspace has skills. A signed-in tool gets the search and enrich permissions by default.

Add skills when you want ChatGPT to follow Vamo's own search methods. Skills and the MCP server can sit side by side.

If your workspace has no skills, you have two choices. Connect the MCP server and ask in plain language. Or ask ChatGPT to read a skill's page from the skills catalog and follow it.

What you need

• A Vamo account on a Pro or Enterprise plan. Approving a sign-in needs one.
• A role that can create keys: owner, admin or user. A read-only member cannot approve a sign-in.
• A ChatGPT workspace that lets you add your own tools. On a company workspace an admin may control this.
• For skills that call the Vamo API directly, a key from Set up > API keys. It is shown once.

Where to get the current steps

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

Open the Set up > Get started at Set up > Get started and choose ChatGPT. It gives you the address to add and says where it goes. Your browser then opens for you to sign in.

For skills, follow the skills install page. It covers ChatGPT alongside the other tools.

Skills and the Vamo API

Vamo skills call the Vamo API over the network. A ChatGPT chat reaches outside services through the tools its workspace has connected. So a chat may not be able to reach api.vamotalent.ai directly.

If that happens, connect the Vamo MCP server and use the skills with it. The skills then guide ChatGPT, and the MCP server does the searching.

On a company workspace

A company workspace can decide which tools its members may add. If you cannot add Vamo, your admin has to allow it first. ChatGPT Business and Enterprise admins covers what to ask them for.

Ask your admin rather than switching to a personal account.

What a first good result looks like

Start a new chat 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. ChatGPT then appears under Connected tools at Set up > API keys, with who approved it. Removing it there disconnects it.

What commonly goes wrong

• You cannot add Vamo. Your company may not let members add their own tools. 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.
• Vamo worked, and now ChatGPT cannot see its tools. This can follow a change to Vamo's tools. See Vamo's tools are missing.
• ChatGPT asks you to sign in again. A signed-in tool must sign in again after 90 days without use.

If something is not working