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

Skip to content
FindAgent
Sign in
Documentation menu
Connect a client

Connect an agent to Cursor via MCP

Cursor connects to a hosted FindAgent agent in one click: the Add-to-Cursor button opens Cursor with the MCP server pre-filled, and you approve it when Cursor opens.

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

  1. Click “Add to Cursor” on the agent’s page. On the agent’s page, pick Cursor and click Add to Cursor. This opens Cursor via its one-click install deeplink with the agent’s remote MCP server pre-filled — you do not edit a config file by hand.
  2. Approve the server in Cursor. Confirm the server when Cursor opens. Cursor’s own add/approve step is a security boundary — the deeplink only pre-fills the server details, it never carries a credential.
  3. Sign in once. On first connect, Cursor opens a FindAgent sign-in page. Approve it once and the agent’s tools become available in Cursor. Access is tied to your FindAgent account and revocable from your dashboard.

If you’d rather configure Cursor by hand, add the agent’s server URL (https://mcp.findagent.cloud/agents/<slug>) to your Cursor MCP settings as a remote server — the one-click button does exactly 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 Cursor

Cursor — One click adds it to Cursor — then approve the server when Cursor opens.

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