Corey Corey
Start with Corey
GuidesHow it worksWhat is insidePricingDocsStart with Corey
Any MCP client

Built on Claude. Connected by a standard.

Corey was designed and written by Claude, and Claude is still where we test first. But Corey reaches you as a remote MCP server, and MCP is an open standard - so the client is yours to choose. Two requirements, no exceptions, listed honestly below.

Start with Corey →See the tested clients
The one-paragraph version

What MCP actually means here.

MCP is a standard way for an AI app to plug into an outside service. Corey publishes itself as one of those services, so instead of us shipping a separate Corey for every app, any app that speaks MCP picks up the whole of Corey as it stands. That is why adding a new client costs you a config line rather than a migration.

Two requirements

What your client needs.

01

Remote MCP over HTTP

Corey is hosted, not installed. Your client needs to talk to an MCP server at a URL (streamable HTTP), rather than only launching local ones as a subprocess.

02

OAuth sign-in

You sign in to Corey through your browser and the client stores and refreshes the tokens. There is no API key to issue, so a client that can only send a static token cannot connect.

the only detail your client needs
https://mcp.getcorey.ai/mcp

No API key, no token, no secret. You sign in through your browser and the client keeps the session.

Said plainly

What we have tested, and what we have not.

"Works with everything" is the kind of claim that costs you an afternoon. Here is the real state of it.

Tested

Checked on every release. These are the paths our setup docs cover.

  • Claude Desktop
  • Claude Code (CLI)
  • Cursor
  • Codex

Should work

Meets both requirements, so Corey should connect. We have not put these through a release check, so tell us if one misbehaves.

  • Other editors with remote MCP support
  • Desktop chat clients that added remote MCP
  • Your own MCP client

Will not work

Missing one of the two requirements. Nothing we can do at our end - the gap is in the client.

  • Local stdio-only MCP clients
  • Clients with no OAuth flow
  • Anything without MCP support at all

Got Corey running somewhere not listed? Tell us at kristian@pressonetwork.com and we will add it.

Questions

The ones people actually ask.

MCP is a standard way for an AI app to plug into an outside service. Corey publishes itself as one of those services, so any app that speaks MCP can pick Corey up and use everything it can do, without us building a separate version for each app.
Corey is built by Claude, on Claude, and for people who use Claude - that is genuinely how it was made and Claude remains the reference client. It is not a Claude product in the sense of being locked to it. The connection is a standard one, so other clients work too.
Find where it stores MCP servers, add one pointing at the Corey URL, and start its sign-in flow. Most clients call it "add a remote MCP server" or "add a custom connector". If it connects and Corey answers whoami, you are done.
Corey itself is identical - same memory, same tools, same approvals. What varies is how well the client renders long tool output and whether it can run things unattended. That is a difference in the chair, not the operator.
File access comes from the client, not from Corey. Whichever client you use has to be pointed at the folder Corey should work in and given permission to read and write there. Check that first before assuming the connection failed.

Bring your own client.

The first 28 days are on us, no card. Start in whichever tool you already have open.

Start with Corey →All integrations