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

Skip to content
Documentation menu
Using agents

Connect a hosted agent

Connecting is the primary way to use an agent. A hosted agent runs on FindAgent and is reachable over MCP — there is nothing to download and nothing to keep running locally. You add its server URL as a remote connector in your AI client and sign in once.

Where the URL comes from
Each agent's page shows its hosted MCP server URL in the form https://mcp.findagent.cloud/agents/<slug>. If you'd rather run everything — including credentials — on your own machine, install locally instead.
One-click for many clients
On an agent's page, clients that publish a documented install link — Cursor, VS Code, LM Studio, and Claude — get a one-click Add to… button that opens the client with the server pre-filled. Every other client gets a Copy server URL button and a one-line paste instruction. Either way you still approve the server once inside your client — that in-client step is a security check, so there is no button that adds a server without your confirmation, and no credential is ever placed in a link.

How connecting works

  1. Pick your client, then add the server. On the agent's page, choose your client. For Cursor / VS Code / LM Studio / Claude, click Add to…. For any other client, copy the server URL and paste it where your client adds a remote MCP server or custom connector.
  2. Approve the server. Confirm the server in your client when it opens (or after you paste the URL).
  3. Sign in once. The first time you connect, your client opens a FindAgent sign-in page. Approve once and you're connected — no API key or token to copy. Access is tied to your FindAgent account and you can revoke it anytime from your dashboard.

Add the connector in your client

A hosted agent is served over a client-agnostic MCP gateway URL, so it works with EVERY MCP-capable client — you are never locked to a subset. A few examples:

  • Claude (web & desktop): one-click Add to Claude, or Settings → Connectors → Add custom connector.
  • Cursor · VS Code · LM Studio: one-click Add to… opens the client with the server pre-filled.
  • ChatGPT (Plus / Pro): Settings → Connectors → add a remote MCP server, then paste the URL.
  • Windsurf · Cline · Continue · Zed · Gemini CLI · Goose · JetBrains · Warp: add it to the client's MCP config file (the agent page shows the exact snippet).
  • Any other MCP-capable client: add the URL as a remote / streamable-HTTP MCP server.

Config file clients

For clients configured by file — Cursor, VS Code, Windsurf, Claude Desktop, Gemini CLI — add the server to your mcp.json (in Claude Desktop: Settings → Developer → Edit Config):

mcp.json
{
  "mcpServers": {
    "findagent-atlas": {
      "url": "https://mcp.findagent.cloud/agents/atlas"
    }
  }
}

Terminal / coding agents

Claude Code can add a remote server straight from the terminal:

terminal
claude mcp add --transport http findagent-atlas https://mcp.findagent.cloud/agents/atlas

Adding the server isn't enough on its own — you still have to sign in. Type /mcp inside Claude Code, pick the server (e.g. findagent-atlas), choose Authenticate, and approve the FindAgent sign-in page that opens. After that the agent's tools appear automatically.

Other CLI agents (for example Codex) add a remote MCP server with the same URL in their own MCP config, then run their own connect/authenticate step.

Which clients support remote MCP

15+ MCP clients can connect to a hosted FindAgent agent (this list is driven from the same registry the agent pages render, so it stays current):

ClientOne-clickHow to add
Claude (web & desktop)YesOne-click “Add to…” or copy URL
ChatGPT (Plus / Pro)Settings → Connectors (paste URL)
CursorYesOne-click “Add to…” or copy URL
VS Code (Copilot)YesOne-click “Add to…” or copy URL
Claude CodeTerminal command (claude mcp add)
Gemini CLIConfig file (~/.gemini/settings.json)
WindsurfConfig file (~/.codeium/windsurf/mcp_config.json)
ClineConfig file (cline_mcp_settings.json)
ContinueConfig file (.continue/config.yaml)
ZedConfig file (settings.json)
LM StudioYesOne-click “Add to…” or copy URL
GooseYesOne-click “Add to…” or copy URL
JetBrains AI AssistantConfig file (mcp.json)
WarpConfig file (Warp → MCP servers)
PostmanSettings → Connectors (paste URL)
Install vs connect
Connecting needs no local runtime, which is what makes a hosted agent reachable from web and mobile clients. If you'd rather keep everything — including credentials — on your own machine, install locally instead.