Use the Vamo MCP server and the API together

An agent with both uses the MCP server for interactive search and the API for batches and repeat runs. The two are set up separately. Connecting MCP does not give an agent the API reference, an API key or permission to make web requests.

What each one is for

MCP is the conversational route. You ask a question, the agent searches, and you read the answer. Then you ask again. It suits exploring a role, trying a different angle and looking closely at a few people.

The API is the programmed route. The agent writes code that calls Vamo with an API key. That code can be saved and run again. It suits working through a long input, such as a file of GitHub logins. It also suits a job that repeats on a schedule.

One test covers most cases. If you will read each answer before choosing the next step, use MCP. If the steps are known before you start, use the API.

What MCP does not give the agent

With MCP connected, the agent sees the Vamo search tools. It reads Vamo's guide and writes a small program for each ask. That program can only call Vamo's search operations. What code mode is explains this.

The connection stops there. It does not hand over three things the API route needs.

• The API reference. The guide the agent reads over MCP covers the search tools. The API is documented separately.
• An API key. A tool that signed in through the browser holds no key at all.
• Permission to make web requests. Some AI tools block the agent from reaching outside addresses until someone allows them. MCP connections are not subject to that setting in those tools, so MCP can work while the API is blocked.

So an agent that searches well over MCP may be unable to call the API. That is expected. It means the API side has not been set up yet.

The two routes can also hold different permissions. A tool that signed in gets a default set for searching and enriching. An API key has the permissions chosen when it was created. The MCP server cannot read account or usage information. The API can tell an agent which plan and permissions its key has.

Give the agent the API on purpose

Set up three things, each one deliberately.

1. Create a key at Set up > API keys. Keys are on the Pro and Enterprise plans. Choose the permissions the job needs and no more. The key is shown once.
2. Point the agent at the API reference. The skills catalog is another way to teach an agent to call the API well.
3. Make sure the agent can reach api.vamotalent.ai. In a company workspace, an owner may need to allow it.

Give a coding agent the Vamo API covers this setup in full.

Use one route for each task

Do not run the same work over both. The work is done twice. You also end up with two sets of results to compare.

An agent with both will sometimes pick for itself. Tell it which one you want.

Use the Vamo MCP tools for this search. Do not call the Vamo API.

Run this as a batch on the Vamo API. Do not use the Vamo MCP tools for it.

Moving from one to the other is fine. Explore over MCP until the ask is right. Then have the agent run the settled version on the API, once.

What to do next

If you have not chosen a route yet, read MCP, skills and the API. If batches are running more often than you expect, read Keep agent usage in check.