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.

claude.ai → your initials (bottom-left) → Settings → Connectors
Add custom connector
Name it Recursiv, paste the address above → Add
Click Connect, sign in, and approve
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.

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.

Settings → turn on Developer mode (search Settings for “Developer mode” if the label has moved — it’s in beta)
Apps & Connectors → Create (the +)
Name Recursiv, paste the address, Authentication: OAuth, create
Open it under Drafts and switch its tools on
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.

gemini.google.com on a computer → Settings & help → Connected Apps
Under Custom apps for Spark → Add a custom app
Paste the address, sign in to Recursiv, approve

Prefer the terminal? Gemini CLI: gemini mcp add --transport http recursiv https://api.recursiv.io/mcp

Perplexity

Needs Perplexity Pro, Max, or Enterprise.

perplexity.ai → profile → Settings → Connectors
+ Custom connector → Remote
Paste the address, choose OAuth, save, sign in

Grok

grok.com/connectors → New Connector → Custom
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 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 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.

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 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

Put Recursiv inside your own product — TypeScript SDK and REST API.

See how it works

The model behind agents, apps, memory, and the evidence trail.

Run your own

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.