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

## Steps
1. Add Corey to your Cursor mcp.json: Add a corey entry under mcpServers with just its URL: { "url": "https://mcp.getcorey.ai/mcp" }. Use the global file at ~/.cursor/mcp.json so Corey is available in every project, which is what you want for a personal assistant. You can also add it from Cursor Settings > Tools and MCP > New MCP Server.
2. Authenticate with one click: Open Cursor Settings > Tools and MCP. The corey server shows a Connect button with a Needs authentication label. Click Connect. Your browser opens Corey's sign-in page (powered by WorkOS). Sign in or create your account, then return to Cursor. There is no access token to paste; Cursor stores and refreshes the tokens for you.
3. Open the folder Corey should work in: Open Cursor on the folder you want Corey to manage (for example ~/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.
4. Run the kickoff prompt: Once corey shows connected with its tools, switch the chat to Agent mode and paste the kickoff prompt. Corey confirms the connection, runs the onboarding interview, writes your setup into the folder, and shows you three things it can do for you right now.

## FAQ
Q: Do I need a paid Cursor plan to use Corey?
A: 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.

Q: Is this the live Corey or a self-hosted one?
A: 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.

Q: Should I add Corey globally or per project?
A: 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.

Q: I already added Corey in Claude Code. Can I reuse that?
A: 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.

Corey does this for you. Put Corey to work, 28 days on us: https://getcorey.ai/pricing