Corey Corey
Start with Corey
GuidesHow it worksWhat is insidePricingDocsStart with Corey
Integrations

Run Corey wherever you work.

Corey plugs into the tools you already have open - Cursor, Claude Desktop, the Claude Code CLI, Codex - with a single URL and one click. No token to paste, no install to babysit. Pick your tool and you are connected in two minutes.

Start with Corey →How Corey works

Cursor

Recommended

The recommended home for running Corey on autopilot - scheduled jobs, cloud agents and an iOS app.

Corey + Cursor →

Claude Desktop

Setup guide

Run Corey in the Claude desktop app. The simplest way to start if you prefer a chat window to an editor.

Set up in Claude Desktop →

Claude Code (CLI)

Setup guide

Run Corey from the terminal. Best if you live in the command line and want it beside your other tools.

Set up in the CLI →

Codex

Tested

Run Corey in OpenAI's Codex CLI. Same operator, same memory, a different chair to sit in.

Corey + Codex →

Any MCP client

How it works

Corey is a remote MCP server. Anything that speaks remote MCP with OAuth can run it.

What your client needs →
Built on Claude. Not locked to Claude.

The client is a swap, not a rewrite.

Corey is built by Claude, on Claude, for Claude - and it works just as well in Cursor and Codex. Here is why those two things are not in tension.

Built by Claude, on Claude

Corey was designed and written by Claude, and Claude does the thinking inside it. That is why it behaves like an operator rather than a chatbot, and it is why Claude stays the reference client.

Connected over MCP

Corey is a remote MCP server, not a plugin. Your client is the window, not the engine. Changing client changes where you type, not what Corey knows or what it can do.

Same Corey, any client

Your memory, your workspace and your standing jobs live with Corey. Sign in from Cursor on Monday and Claude Desktop on Tuesday and it is the same operator, mid-sentence.

Tested every release in Claude Desktop, Claude Code, Cursor and Codex · What your client needs →

The same three moves everywhere

A URL, one click, then talk to Corey.

01

Add the URL

Drop the Corey MCP URL into your client's config, or paste it into its MCP settings.

02

Click Connect

Sign in through your browser. Your client stores and refreshes the tokens - nothing to paste.

03

Run the kickoff

Open a folder, switch to Agent mode and paste the kickoff prompt. Corey does the rest.

Questions

Which tool, which plan, and can I change my mind.

No. Corey is built by Claude, on Claude, and Claude is the reference client - but Corey itself is a remote MCP server, so it runs in any MCP client that supports OAuth. We test Claude Desktop, Claude Code, Cursor and Codex on every release.
Only if you run Corey in Claude. You need a plan on whichever client you choose - a Claude plan for Claude Desktop or Claude Code, a Cursor plan for Cursor, a ChatGPT or API plan for Codex. Corey is a separate subscription on top, and the first 28 days are on us.
The operator is identical: same memory, same tools, same approvals. What differs is what the client itself can do around it. Cursor adds scheduled jobs, cloud agents and an iOS app, which is why it is our recommendation for hands-off running.
Yes to both. Nothing about your setup lives in the client, so you can add Corey in a second client at any time and pick up where you left off. Many people run the CLI at their desk and Cursor on their phone.

Connect Corey in two minutes.

Start with the tool you already have open. The first 28 days are on us - no card, hire or fire after.

Start with Corey →See Corey + Cursor