Corey Corey
Hire Corey
How it works Use cases Guides Build log What Corey builds Docs Hire Corey

Corey in Cursor

To use Corey in Cursor, add it as a remote MCP server by putting its HTTPS URL in your Cursor mcp.json, then open Tools and MCP in Cursor Settings and click Connect to sign in through your browser. No token to paste. Then open the folder you want Corey to work in and run the kickoff prompt in Agent mode.

Cursor is a code editor with a built-in AI agent. You can run Corey inside it by adding Corey as a remote MCP server. If you prefer the terminal, use the Claude Code (CLI) guide; if you prefer a chat app, use the Claude Desktop guide.

How this works: a URL and one click, no token

Corey is a remote MCP server served over HTTPS. Cursor speaks Streamable HTTP and has supported the MCP OAuth sign-in flow since v1.0, so all you do is give Cursor the URL and click Connect. Cursor opens your browser, you sign in to Corey, and Cursor stores and refreshes the tokens for you. There is no access token to paste.

Step 1: Add Corey to your Cursor mcp.json

Cursor reads MCP config from two places: ~/.cursor/mcp.json (global, every project) and .cursor/mcp.json (one project). Because Corey is a personal assistant, use the global file so it is available everywhere.

Add a corey entry under mcpServers. A remote server needs only a url:

~/.cursor/mcp.json 
{
  "mcpServers": {
    "corey": {
      "url": "https://mcp.getcorey.ai/mcp"
    }
  }
}

Prefer not to edit JSON by hand? In Cursor, open Settings > Tools and MCP > New MCP Server and add the same URL.

Bringing it over from Claude Code

If you already added Corey in Claude Code, its entry in ~/.claude.json looks almost the same, with one extra field:

Claude Code (for reference) 
"corey": {
  "type": "http",
  "url": "https://mcp.getcorey.ai/mcp"
}

Copy the url and drop the "type" field when you add it to Cursor. Cursor infers the transport from the URL, so the type key is not used.

Step 2: Authenticate with one click

Open Cursor Settings > Tools and MCP. The corey server appears with a Connect button and a Needs authentication label.

  1. Click Connect. Your browser opens Corey’s sign-in page (powered by WorkOS), not Cursor asking for a password.
  2. First time: create your Corey account. This starts your 28-day probation at no cost. Returning: sign in.
  3. Return to Cursor. The corey server now shows connected with its tools listed, ready for the agent to call.

Step 3: Open the folder Corey should work in

Open Cursor on the folder you want Corey to manage, or default to ~/Corey. In Agent mode, Corey reads and writes files in that folder natively, so there is no separate filesystem step like the Desktop app has. Setup is non-destructive: Corey only adds files that are missing and never deletes anything.

Step 4: Run the kickoff prompt

Switch the chat to Agent mode, then paste this as your first message:

shell 
You are Corey. I've just connected you.
1. Run whoami to confirm the connection. If it fails, stop and tell me what to fix.
2. Run onboard and walk me through the Meet Corey interview, one question at a time.
3. Write my setup into this folder as my overlay.
4. Then show me three things you can do for me right now.

Corey confirms the connection, runs the onboarding interview, sets up your workspace in the open folder, and suggests three concrete things it can do for you right now, drawn from what you told it in the interview.

Still not connecting?

  • The dot stays red: confirm the URL is https://mcp.getcorey.ai/mcp (HTTPS, ends in /mcp).
  • The browser did not open: check Cursor’s MCP logs for the authorization URL and open it manually.
  • You copied the entry from Claude Code: remove the "type": "http" line. Cursor only reads url (and headers/auth where needed).
  • Tools still missing after sign-in: toggle the corey server off and on in Settings > Tools and MCP.

Related

Quick start in Claude Code (CLI) Best practices

Questions, answered

Corey works in Cursor's Agent mode, which is available on Cursor's plans, including its no-cost tier, subject to Cursor's own usage limits. The Corey subscription is separate from Cursor; your 28-day Corey probation at no cost starts when you run onboard, with no card required.
This guide connects to the live hosted Corey at https://mcp.getcorey.ai/mcp, the same endpoint used by the Desktop and CLI guides. If you run your own Corey on a server, point the URL at your instance instead and follow its auth method. See Run Corey on a Hetzner VPS.
Add it globally in ~/.cursor/mcp.json so Corey is available in every project, which suits a personal assistant. Use a project-level .cursor/mcp.json only if you want Corey scoped to a single repository.
Cursor uses its own config, so add Corey to mcp.json separately. The entries are almost identical; Claude Code's entry has a "type" field, while Cursor infers the transport from the URL, so copy the URL and drop the "type" field.