> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.recursiv.io/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.recursiv.io/_mcp/server. # Connect Recursiv to your AI You don't have to learn Recursiv. **Your AI does.** Connect Recursiv to the assistant you already use (Claude, ChatGPT, Gemini, Cursor — any of them), point it at Recursiv's knowledge, and then just tell it what you want: *build an app, deploy it, spin up a team of agents, run an eval.* It does the work; you stay in the conversation. Three steps, about two minutes: #### Connect — give your AI the tools Add Recursiv as a connector so your assistant can actually do things in your account. #### Teach — make your AI a Recursiv expert Point it at one URL so it knows every primitive, tool, and pattern. #### Build — do something real right now Copy a prompt, paste it, watch it ship. --- ## Step 1 — Connect Everything uses one address: ``` https://api.recursiv.io/mcp ``` That's the full Recursiv toolset — nothing held back. (On ChatGPT, or any client that caps how many tools it will load, use `https://api.recursiv.io/mcp/app` instead: a leaner, curated set that still covers agents, teams, deploys, memory, data, and evals.) You'll need a **Recursiv account** — if you don't have one, ask whoever invited you for an invite code. When an app asks how to sign in, choose **OAuth** (sometimes shown as "Sign in"): it signs you into your Recursiv account, no keys to paste. Pick your assistant: ### Claude — the simplest Works on the free plan (which allows one custom connector) and every paid plan. 1. [claude.ai](https://claude.ai) → your initials (bottom-left) → **Settings** → **Connectors** 2. **Add custom connector** 3. Name it **Recursiv**, paste the address above → **Add** 4. Click **Connect**, sign in, and approve 5. Recursiv now appears in the tools menu of any chat Same steps in the Claude desktop app; connectors follow you to mobile. For Claude Code or a local setup, see [MCP](/guides/ai-tools/mcp-claude-cursor). ### ChatGPT Needs a paid plan with **Developer mode** on (a beta feature; on Business/Enterprise/Edu an admin enables it first). Set it up on the website, not mobile. 1. **Settings** → turn on **Developer mode** (search Settings for "Developer mode" if the label has moved — it's in beta) 2. **Apps & Connectors** → **Create** (the **+**) 3. Name **Recursiv**, paste the address, **Authentication: OAuth**, create 4. Open it under **Drafts** and switch its tools **on** 5. In a chat, click **+** and enable Recursiv ### Gemini Needs a **personal** Google account (not work/school), access to Gemini **Spark**, you must be **18+ and in the US**, with **"Keep Activity" on**. 1. [gemini.google.com](https://gemini.google.com) on a computer → **Settings & help** → **Connected Apps** 2. Under **Custom apps for Spark** → **Add a custom app** 3. Paste the address, sign in to Recursiv, approve Prefer the terminal? [Gemini CLI](https://github.com/google-gemini/gemini-cli): `gemini mcp add --transport http recursiv https://api.recursiv.io/mcp` ### Perplexity Needs Perplexity **Pro, Max, or Enterprise**. 1. [perplexity.ai](https://perplexity.ai) → profile → **Settings** → **Connectors** 2. **+ Custom connector** → **Remote** 3. Paste the address, choose **OAuth**, save, sign in ### Grok 1. [grok.com/connectors](https://grok.com/connectors) → **New Connector** → **Custom** 2. Paste the address and sign in On a Grok Business/Enterprise team, an admin adds it via **+ Add Connector → Other**. ### Cursor, VS Code, Windsurf, Claude Code These connect to a remote MCP server by URL natively. See [MCP](/guides/ai-tools/mcp-claude-cursor) for the exact per-tool setup. ### Microsoft Copilot Admin-only: an IT admin adds Recursiv inside **Copilot Studio** (**Tools → Add a tool → New tool → Model Context Protocol**, paste the address, **OAuth 2.0**). [Contact us](mailto:support@recursiv.io) and we'll set it up with them. --- ## Step 2 — Teach your AI everything about Recursiv Connecting gives your assistant the *tools*. This gives it the *knowledge*. Paste this into your assistant once: ``` Read https://docs.recursiv.io/llms-full.txt — that's your complete reference for Recursiv. Use it whenever you work with my Recursiv tools. ``` That single file is the entire Recursiv documentation as clean text: every primitive, every tool, every pattern. Your assistant reads it and becomes an expert — no more guessing, no more stale answers. > **Note** > > **Building with code?** Drop a Recursiv `AGENTS.md` into your repo so Cursor, Claude Code, or Copilot are Recursiv-aware in every session. **Claude power user?** A packaged Recursiv Skill is on the way. Ask [support](mailto:support@recursiv.io) for either. --- ## Step 3 — Do something real, right now You're connected and your AI knows Recursiv. Prove it — say one of these to your assistant: #### Ship a real app in one sentence *"Build and deploy a personal site with my bio, links, and a contact form, backed by a database. Give me the live URL."* #### Put a team of agents to work *"Break customer-support triage into steps like a workflow, build a 3-agent team for it, add an eval, and run a test."* #### Prove what it did *"Show me the evidence from that run — cost, latency, and every decision, step by step."* #### See everything at a glance *"What are all my agents and apps doing right now?"* When your assistant does these, you're using Recursiv. Everything else is just more of the same: describe the outcome, let the agent build and measure it, keep the receipts. --- ## Keep building #### [Build with the SDK](/sdk) Put Recursiv inside your own product — TypeScript SDK and REST API. #### [See how it works](/guides/concepts) The model behind agents, apps, memory, and the evidence trail. #### [Run your own](/guides/operations/self-hosting) Self-host Recursiv on your infrastructure. ## Trouble signing in? The OAuth window signs you into your Recursiv account. No account yet, or a permissions error? Ask whoever sent you here for an invite to their organization. App menus move around now and then, but the address and the OAuth sign-in never change.