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 Gemini via MCP

Gemini connects to a hosted FindAgent agent through the Gemini CLI’s MCP config: add the agent’s remote server to your settings.json under mcpServers, then restart the client.

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 Gemini, step by step

  1. Copy the agent’s server URL. On the agent’s page, choose Gemini and copy the agent’s server URL — it looks like https://mcp.findagent.cloud/agents/<slug>.
  2. Add it to ~/.gemini/settings.json. Open your Gemini CLI settings file at ~/.gemini/settings.json and add the server under mcpServers as { "mcpServers": { "findagent-<slug>": { "url": "https://mcp.findagent.cloud/agents/<slug>" } } }. The agent’s page shows the exact prefilled snippet so you can paste it directly.
  3. Restart Gemini and sign in. Restart the Gemini CLI so it picks up the new server. On first use it opens a FindAgent sign-in — approve it once and the agent’s tools are available in Gemini.

The Gemini CLI reads its MCP servers from settings.json; the same remote server URL also works in any other MCP-capable client without change.

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 Gemini

Gemini CLI Add the server to your settings.json, then restart the client.

These steps follow Gemini's own connector flow. Gemini'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, VS Code, mobile, any other MCP client. Prefer to run everything — including credentials — on your own machine? See Install an agent instead.