Corey in Claude Code (CLI)

Corey is served over HTTPS. If you add it as http://..., Claude Code fetches Corey’s protected-resource metadata (which says https://...), sees a mismatch, and refuses to authenticate with exactly this error:

Protected resource https://mcp.getcorey.ai/mcp does not match expected http://mcp.getcorey.ai/mcp

The fix is just the scheme. Keep reading.

If you tried to add Corey before and used http://, remove it first:

claude mcp remove corey

If you have never added Corey before, skip this step.

No token, no header. Corey uses browser sign-in, not a pasted key. The --scope user flag makes Corey available in every project, which is what you want for a personal assistant:

claude mcp add --transport http corey https://mcp.getcorey.ai/mcp --scope user

Already added Corey in the Desktop app? Import it instead of retyping:

claude mcp add-from-claude-desktop

Open a Claude Code session (from the folder you want Corey to work in) and run:

/mcp

Select corey, then Authenticate. Your browser opens Corey’s sign-in page.

The browser page is Corey’s own sign-in (powered by WorkOS), not Claude asking for your Claude password. It is where you:

• First time: create your Corey account (email and password, or a social login if shown). This creates your account and starts your 28-day probation at no cost.
• Returning: sign in.

After you finish in the browser, return to the terminal. /mcp now shows corey connected with its tools. There is no access token to paste.

Once corey shows connected, paste this as your first message:

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 current folder, and suggests three concrete things it can do for you right now, drawn from what you told it in the interview.

Claude Code reads and writes local files natively, so Corey builds your workspace in the current folder. There is no separate Cowork step (unlike the Desktop app). Run Claude Code from the folder you want Corey to work in, or default to ~/Corey.

Want to type corey from anywhere to jump into your Corey folder and start a session? The onboarding can install a small shell function for you (corey-launcher.sh, idempotent). After it runs:

source ~/.zshrc   # or ~/.bashrc
corey

corey (or Corey) changes into your Corey folder ($COREY_HOME, default ~/Corey) and launches Claude with a short greeting.