Do I need an API key to connect Corpus?

Not for clients that implement the MCP authorization spec. Claude Code and Codex discover the authorization server, register themselves and open your browser to approve, with no key to copy. Clients that do not support it yet, such as Cursor, use a key minted in the console under Memory then MCP Access.

What is the Corpus MCP endpoint?

https://console.edgex11.com/api/v1/runtime/mcp — a remote MCP server over Streamable HTTP. Every client points at the same URL and shares the same memory.

Which clients work with Corpus?

Any client that speaks MCP over HTTP. Codex and Claude Code are verified and connect over OAuth with no key. Windsurf, Cline and Zed take the same URL. Cursor does not implement the MCP authorization spec yet, so it uses a key instead.

Is Corpus a local or a remote MCP server?

Remote. There is nothing to install and no process to run locally. The endpoint is hosted, so the same memory is available from every machine and every tool you sign in from.

What access am I granting?

Three scopes exist: memory:read, memory:write and memory:admin. The consent screen shows which are being requested before you approve.

Does Corpus work with Cursor?

Yes, using a key rather than OAuth. Cursor does not implement the MCP authorization spec yet, so mint a key in the console under Memory then MCP Access and send it with the same endpoint as an Authorization: Bearer header. The key carries the same memory:read, memory:write and memory:admin scopes as an OAuth grant.

How do I revoke a client's access?

In the console under Memory then MCP Access. Revocation takes effect immediately, and the authorization server exposes a standard OAuth revocation endpoint.

Documentation

Connect Corpus over MCP.

One command. Your client detects OAuth, registers itself and opens your browser to approve. There is no API key to copy and nothing to paste into a config file.

Connect

One command per client.

Every client points at the same endpoint and shares the same memory.

CodexVerified

codex mcp add edgex-memory --url https://console.edgex11.com/api/v1/runtime/mcp

Codex prints “Detected OAuth support”, registers itself and opens the browser. There is no separate login step.

Claude CodeVerified

claude mcp add --transport http edgex-memory https://console.edgex11.com/api/v1/runtime/mcp
claude mcp login edgex-memory

Claude Code adds the server first, then login runs the browser approval.

Any OAuth-capable client

# Streamable HTTP endpoint — no headers needed
https://console.edgex11.com/api/v1/runtime/mcp

Windsurf, Cline and Zed take the same URL. Any client that implements the MCP authorization spec discovers the rest on its own.

Clients without OAuth

Key-based access still works.

Not every client implements the MCP authorization spec yet — Cursor among them. Those take the same endpoint with a key you mint yourself.

Bearer key

claude mcp add --transport http edgex-memory https://console.edgex11.com/api/v1/runtime/mcp \
  --header "Authorization: Bearer YOUR_KEY"

Mint the key in the console under Memory › MCP Access. Any client that accepts a custom header takes the same pair — the endpoint above, and an Authorization: Bearer header carrying your key. Keys carry the same memory:read, memory:write and memory:admin scopes as an OAuth grant, and are revoked from the same screen.

What your client does

Discovery, then one approval.

Nothing here needs doing by hand. It is written down because knowing what a tool did on your behalf is the point of governed access.

The endpoint says where to authenticate
The first call returns 401 with a WWW-Authenticate header naming the protected-resource metadata document.
Your client registers itself
It reads the authorization-server metadata and registers dynamically. Nothing is pre-provisioned, and no client secret is shared with you.
You approve in the browser
Authorization code with PKCE. You see the scopes before granting them, and the token is bound to this resource.

Reference

The details, if you need them.

Endpoint: https://console.edgex11.com/api/v1/runtime/mcp
Transport: Streamable HTTP
Authorization: OAuth 2.1 — authorization code with PKCE (S256), dynamic client registration, refresh and revocation
Scopes: memory:read, memory:write, memory:admin
Resource metadata: /.well-known/oauth-protected-resource
Server metadata: /.well-known/oauth-authorization-server
Revoking access: Console › Memory › MCP Access. Revocation takes effect immediately.

One memory. Every tool.

Connect one repository and point every client at it. Free to start, no credit card — see pricing.

Start free What Corpus is

Connect Corpus over MCP.

One command per client.

Key-based access still works.

Discovery, then one approval.

The endpoint says where to authenticate

Your client registers itself

You approve in the browser

The details, if you need them.

One memory. Every tool.