# Corey in Codex

To use Corey in Codex, add an mcp_servers.corey block to ~/.codex/config.toml with the Corey URL, then run codex mcp login corey to sign in through your browser. Codex treats a server with a url as a remote streamable-HTTP server and defaults its auth to OAuth, so there is no token to paste. Then open the folder you want Corey to work in and run the kickoff prompt.

## Steps
1. Add Corey to your Codex config: Open ~/.codex/config.toml and add an [mcp_servers.corey] block with a single url key pointing at https://mcp.getcorey.ai/mcp. Codex treats any server with a url as a remote streamable-HTTP server, and its auth setting defaults to oauth, so the URL is all you need. The codex mcp add command is for local stdio servers, so a remote server like Corey goes in the config file.
2. Sign in with codex mcp login: Run codex mcp login corey. Codex opens your browser at Corey's sign-in page (powered by WorkOS). Create your account the first time, which starts your 28-day probation at no cost, or sign in if you are returning. Codex stores and refreshes the tokens for you, so there is no access token to paste and no secret in your config file.
3. Open the folder Corey should work in: Start Codex in the folder you want Corey to manage, for example ~/Corey. Corey reads and writes files in that folder through Codex. Setup is non-destructive, so pointing it at an existing folder is safe - Corey only adds files that are missing and never deletes anything.
4. Run the kickoff prompt: Paste the kickoff prompt as your first message. Corey confirms the connection with whoami, runs the Meet Corey interview one question at a time, writes your workspace into the open folder, builds your Command Center and then shows you three concrete things it can do for you right now.

## FAQ
Q: Do I still need a Claude subscription to use Corey in Codex?
A: No. You need a plan on whichever client you run Corey in, so for Codex that is your ChatGPT or API access. The Corey subscription is separate and identical either way - 28 days on us with no card, then £9 every 4 weeks or £90 a year.

Q: Is this the same Corey that runs in Claude Desktop?
A: Yes, exactly the same one. Corey is a hosted remote MCP server, so every client is a window onto the same operator. Your memory, workspace, standing jobs and approval gates are identical whichever client you sign in from, and you can run more than one client at once.

Q: Why does codex mcp add not work for Corey?
A: The codex mcp add command registers local stdio servers, which Codex launches as a subprocess. Corey is a remote server reached over HTTPS, so it is configured by adding an mcp_servers block with a url key to ~/.codex/config.toml instead.

Q: Is it safe to commit my Codex config with Corey in it?
A: Yes. The block contains only the public Corey URL - no API key, no bearer token, no secret of any kind. Authentication happens through the browser sign-in flow and the tokens are stored by Codex, not written into the config file.

Corey does this for you. Start with Corey, 28 days on us: https://getcorey.ai/get-started