Corey Corey
How it worksWhat Corey buildsCase studiesYour dataDocsStart with Corey
Corey × Cursor

Your operator, working on autopilot.

Corey is the operator you hire to run your business. Cursor is where it never clocks off - scheduled jobs, cloud agents and a phone in your pocket. Connect the two and the work keeps running while you steer.

28 days on us, no card · Connects in two minutes over MCP · No token to paste

cursor · agentauto-run
✓ corey connected · mcp.getcorey.ai
/loop every day 07:00
reconcile invoices vs bank feed
✓ matched 212 / 218
! 3 flags held for you
agent (cloud)
drafting the Monday report…
⏸ awaiting your approval
Remote MCP, one clickNo token to pasteYou approve every actionWorks on Cursor's free tier
The pairing

Corey does the work. Cursor makes it hands-off.

On its own, Corey is a brilliant operator you talk to. Put it inside Cursor and it stops waiting for you - it runs on a schedule, works in the cloud and reports back when there is a decision to make.

THE OPERATOR

Corey

Plans the work, dispatches specialists and runs to your overlay - your facts, voice and guardrails.

THE RUNTIME

Cursor

Agents, /loop, cloud machines and an iOS app - the runtime that keeps the work going when you are away.

THE RESULT

Autopilot

A business that runs its standing jobs on its own, and only pings you for the calls that need a human.

What running on autopilot looks like.

Real, recurring work that runs itself once you set it up - each one a Corey job on a Cursor mechanism. You still approve anything that ships, sends or spends.

Every morning at 07:00

Reconcile before you wake

Corey matches the invoices to the bank feed and holds the odd ones for you. Runs itself on a schedule.

via /loop
While you sleep

Triage and tee up PRs

A cloud agent works on its own machine - groups the issues, drafts the replies, opens PRs for your review.

via cloud agents
Every Friday

The weekly report writes itself

Corey pulls the numbers, writes the Monday summary and lists three things to watch, queued for your sign-off.

via automations
From the train

Kick it off from your phone

Launch a job or remote-control the agent on your desk from the Cursor iOS app. Approve and ship from your pocket.

via Cursor for iOS
Before anything ships

Reviewed, not rubber-stamped

Run /review and Bugbot catches the issues before they land. Corey never pushes work you have not seen.

via /review
All day

Longer runs, fewer taps

Auto-review run mode lets Corey work through a long job with fewer interruptions and safer execution.

via auto-review
Two minutes

Add Corey to Cursor.

Corey is a remote MCP server. You give Cursor a URL and click Connect - no token to paste. Here is the whole thing.

  1. 01

    Add Corey to your Cursor mcp.json

    Put the Corey URL in ~/.cursor/mcp.json so it is available in every project. A remote MCP server needs only its URL, no token to paste.

  2. 02

    Click Connect and sign in

    Open Cursor Settings > Tools and MCP. The corey server shows Connect. Click it, sign in through your browser, and Cursor stores and refreshes the tokens for you.

  3. 03

    Open the folder Corey should run

    Open Cursor on the folder you want Corey to manage, for example ~/Corey. In Agent mode it reads and writes files there natively. Setup is non-destructive.

  4. 04

    Run the kickoff prompt

    Switch the chat to Agent mode and paste the kickoff prompt. Corey confirms the connection, runs the onboarding interview, writes your overlay and shows three things it can do right now.

~/.cursor/mcp.json
// global - Corey in every project
{
  "mcpServers": {
    "corey": {
      "url": "https://mcp.getcorey.ai/mcp"
    }
  }
}
kickoff prompt · Agent mode
You are Corey. I've just connected you.
1. Run whoami to confirm the connection.
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.
Coming from Claude Code? Copy the URL and drop the "type"field - Cursor infers the transport. Full walk-through in theCorey in Cursor doc.

The Cursor link is our referral - you get extra trial credit, it credits us, same price either way.

The toolkit

The Cursor features that do the driving.

These are the parts of Cursor that turn Corey from something you talk to into something that runs on its own. Newly shipped, and worth learning.

/loop

Runs a prompt on a local schedule until an outcome is met. This is how a Corey job becomes a standing job.

Cloud agents

Agents work on their own machines to build, test and demo end to end. Corey keeps going while your laptop is shut.

Automations

Schedule or trigger agents to run on their own. Set the recurring work once and let it run.

Cursor for iOS

Launch always-on agents or remote-control your desk from your phone. Live updates, ship PRs on the move.

Auto-review

A run mode for longer, safer, less interrupted execution. Set it in Settings > Agents > Approvals & Execution.

Bugbot / /review

Cursor's review agent spots and fixes issues before merge - now faster, cheaper and sharper.

Honest about cost

Two subscriptions, both free to start.

Corey and Cursor are separate bills. You can trial both at no cost before you spend a penny.

YOUR OPERATOR

Corey

£49/month

or £490/year · first 28 days on us, no card

The agent that runs your business and does the real work. The sale happens in the chat - hire or fire after 28 days.

See Corey pricing →
THE RUNTIME

Cursor

Free, then $20/mo

Hobby tier free · Pro from $20/month · Teams $40/user

The editor Corey runs in. Corey works on the free tier; Pro unlocks bigger agent limits, cloud agents and Bugbot.

Get Cursor (referral) →

Questions before you connect.

They are two separate subscriptions. Corey is your operator and starts with a 28-day probation at no cost, no card. Cursor is the editor you run it in and has a no-cost tier plus paid plans from $20/month. You can trial both for free before spending anything.
This connects to the live hosted Corey at https://mcp.getcorey.ai/mcp, the same endpoint used by the Claude Desktop and CLI guides. If you run your own Corey on a server, point the URL at your instance instead.
Add it globally in ~/.cursor/mcp.json so it is available in every project, which suits a personal operator. Use a project-level .cursor/mcp.json only if you want Corey scoped to a single repository.
Corey runs the same in Claude Desktop and the Claude Code CLI. Cursor is the recommendation when you want the hands-off extras - /loop, cloud agents, automations and the iOS app - so the work keeps running when you are not at the keyboard.
Cursor uses its own config, so add it to mcp.json separately. The entries are almost identical. Copy the URL and drop the "type" field - Cursor infers the transport from the URL.

Put your business on autopilot.

Start Corey, drop it into Cursor, and hand over the jobs you keep doing by hand. The first 28 days are on us - keep it running only if it earns its place.