BetaFindAgent is in free public beta — every agent is free to connect and paid agents aren't available yet.

Skip to content
Documentation menu
Connect a client

Connect an agent to VS Code via MCP

VS Code (with Copilot) connects to a hosted FindAgent agent in one click: the Add-to-VS-Code button opens VS Code with the MCP server pre-filled, and you confirm it when VS Code opens. There is a separate button for VS Code Insiders.

What you’re connecting to
A hosted FindAgent agent runs on FindAgent and is reached over a Model Context Protocol (MCP) server URL of the form https://mcp.findagent.cloud/agents/<slug>. Each agent's page shows its exact URL and the one-click / copy button for this client. No credential is ever placed in a connect link — you enter any per-agent credentials after connecting.

Connect to VS Code, step by step

  1. Click “Add to VS Code” on the agent’s page. On the agent’s page, pick VS Code and click Add to VS Code (or the Insiders button if you run VS Code Insiders). This opens VS Code via its one-click MCP install link with the agent’s remote server pre-filled.
  2. Confirm the server in VS Code. VS Code shows the server it is about to add — confirm it. VS Code’s own confirm step is a security boundary; the deeplink only carries the public server URL, never a credential.
  3. Sign in once. On first connect, VS Code opens a FindAgent sign-in page. Approve it once and the agent’s tools appear in Copilot. Access is tied to your FindAgent account and revocable anytime.

To add it by hand instead, put the agent’s remote server (https://mcp.findagent.cloud/agents/<slug>) into your .vscode/mcp.json as an http server — the one-click button does this for you.

The server URL

Every hosted agent connects at the same client-agnostic gateway URL, so once you know an agent's slug you know its URL:

server URL
https://mcp.findagent.cloud/agents/atlas

Replace atlas with the agent you want — the agent's page always shows the exact URL to copy.

About connecting to VS Code

VS Code (Copilot) One click adds it to VS Code — then confirm the server in VS Code when it opens.

These steps follow VS Code's own connector flow. VS Code's MCP docs cover the client side in more detail.

Other clients + local install

Connecting works the same way for every MCP-capable client — see the full connect guide for the whole client list, or the per-client guides for Claude, ChatGPT, Cursor, Gemini, mobile, any other MCP client. Prefer to run everything — including credentials — on your own machine? See Install an agent instead.