Connect
MCP with OAuth
Connect any MCP client to HyperMemory by URL, and sign in with your browser
This is the recommended way to connect an MCP client: paste one URL, sign in, done. There are no keys to manage, and tokens refresh in the background.
Server URL
https://api.hypermemory.io/mcpTransport: Streamable HTTP. Authentication: OAuth 2.1 with PKCE, discovered automatically.
Connect
- Add a remote MCP server in your client with the URL above. Name it HyperMemory.
- Your client opens your browser on HyperMemory’s sign-in page.
- Sign in with email and password, Google or GitHub — or create an account.
- Approve the connection.
The 18 hm_* tools are now available to your agent.
Client guides
| Client | How |
|---|---|
| Claude Code | Plugin (recommended) or claude mcp add --transport http hypermemory https://api.hypermemory.io/mcp |
| Codex | Plugin (recommended) or [mcp_servers.hypermemory] in ~/.codex/config.toml |
| claude.ai chat | Custom connector |
| ChatGPT | Developer mode connector |
| Cursor | ~/.cursor/mcp.json |
| OpenClaw | MCP config or native plugin |
| Windsurf, VS Code and other MCP clients | Add a remote (HTTP) MCP server with the URL above |
Give the agent the HyperMemory protocol
Connecting gives an agent the tools; the HyperMemory skill teaches it to use them every turn — recall before replying, save what it learns, report token usage. The plugins install it for you. Elsewhere, ask your agent to fetch it:
Get the latest HyperMemory skill with hm_skill and follow it.
Organizations
If you belong to an organization, recall searches its memory alongside yours. If you belong to several, tell the agent which organization a project uses — it sends that choice as organization_id. See Organization memory.
When to use an API key instead
Use MCP with an API key when:
- the client can’t run a browser sign-in (servers, CI, containers);
- you want the agent bound to a specific graph other than your default;
- you’re calling MCP over raw HTTP.
See OAuth for the endpoints and token lifetimes.