# Onboard yourself to Vamo

You are an AI agent. Work through the steps below in order, then report back to
the user. Do not skip step 2: it proves the connection before you rely on it.

Vamo is a recruiting platform for engineering talent. Through this server you can
Search GitHub for developers, read their public work, build shortlists on a
project, and run outreach sequences.

## 1. Get access and add the server

- Endpoint: `https://mcp.vamotalent.ai/mcp/platform`
- Transport: remote MCP over Streamable HTTP
- Auth: a browser sign-in, or an `Authorization: Bearer <key>` header set from a
  key stored on this machine

Never ask the user to paste an API key. Take the first of these that applies.

- **The user's message has a setup code.** It starts with `vamo_xc_`. Fetch
  https://vamotalent.ai/agents/connect.md and follow it with that code. It
  asks the user how to connect, and on the key way stores the key on this
  machine and adds a Vamo server to the user's tool.
  In its step 6, use `https://mcp.vamotalent.ai/mcp/platform` as `mcpUrl`.
- **No code, but a key is already stored on this machine.** That is the file
  `~/.config/vamo/env`, or `%USERPROFILE%\.config\vamo\env` on Windows.
  Check that it exists without printing it. If it does, add this server with
  step 6 of https://vamotalent.ai/agents/connect.md, using
  `https://mcp.vamotalent.ai/mcp/platform` as `mcpUrl`.
- **Neither, and your tool can sign in to an MCP server with a browser.**
  Claude Code, Claude Desktop and ChatGPT can. Add `https://mcp.vamotalent.ai/mcp/platform` as a remote
  MCP server with no key and no header. In Claude Code that is
  `claude mcp add --transport http vamo https://mcp.vamotalent.ai/mcp/platform`, then `/mcp`, pick vamo
  and sign in. In a chat app you cannot add it yourself: tell the user to add a
  custom connector with that address in the app's connector settings. Their
  browser opens on a Vamo sign-in page. Have them approve it. That way needs no
  key and no setup code.
- **None of these.** Say this to the user, then stop until they answer:

  > Open Vamo Home at https://app.vamotalent.ai/setup/get-started, press **Copy setup prompt**
  > and paste it here.
  > For a tool that signs in with a browser, **Set up by hand** on that page gives the server address instead.

  What comes back is one of two things. A line with a setup code: follow it as
  in the first case. Or, for a tool that signs in with the browser, a server
  address or the command that adds it: add the server to the tool that way,
  with `https://mcp.vamotalent.ai/mcp/platform` as its address, and have the user approve the sign-in
  page when it opens. That way needs no key.

## 2. Confirm the connection with a documentation call

Reload your MCP servers, then call `explore_docs`. A successful response here
means the transport and the URL are correct. A server that was only just added
may not show its tools until the client restarts: if your client does not know
the server yet, tell the user to restart it and stop here.

If the call fails, fix the connection before going further. Report the exact
error to the user rather than guessing at a key.

## 3. Verify with one authenticated call

Call `account_execute` and read the account back. It confirms the key resolves
and carries permissions.

## 4. Report what you can now do

Tell the user which topics answered, what the key's permissions allow, and what
you would need granted to do more.

## How these tools work

There are four topics: Explore, Outreach, Projects, and Account. Each one has a
pair of tools:

- `<topic>_docs` returns typed documentation for the endpoints in that topic.
- `<topic>_execute` runs JavaScript you write in an isolated sandbox, with a
  client already bound to the user's account.

So you are not calling hundreds of endpoints one at a time. You read the
documentation for a topic, then write one piece of code that chains the calls,
filters, and aggregates, and you get one result back. Always read a topic's
documentation before writing code against it. The documentation is generated from
the live API, so it is accurate at the moment you read it.

## Rules

- Documentation tools only describe the API. Execute tools act on the user's
  account.
- The key carries only the permissions the user granted. A call outside them
  returns 403. Do not retry it. Tell the user which permission is missing.
- Anything that contacts a real person goes through outreach. Confirm with the
  user before you send.