One URL for ChatGPT, Claude, Gemini and Perplexity. One line for Codex, Claude Code, Cursor and VS Code.
Agentu speaks the Model Context Protocol (MCP), so every AI app that supports connectors can use your memory. Inside the app, the Connect AI apps screen will offer one button per app (in build); until then, these are the steps. Which plans and caveats apply to each app is on the models page.
https://memory.agentu.com and the MCP URL is https://memory.agentu.com/mcp. Both are shown again, filled in, on the page where your key is created.Claude as a custom connector
- In claude.ai or Claude Desktop open Settings → Connectors → Add custom connector. The Connect page of the Agentu web app opens this dialog with the values prefilled.
- Name it Agentu Memory and paste
https://memory.agentu.com/mcp, then Add and Connect. - Claude opens Agentu's consent page. Paste a key — ideally a narrow one such as
read:Work, write:Work— and choose Allow. - In a conversation, enable the connector. Claude now has seven tools:
recall,remember,remember_many,remember_file,find_file,list_categoriesandlist_projects(what each does is in the Any MCP client tab).
Behind the scenes this is OAuth 2.1 with PKCE: Claude never sees your key, only a token bound to it. Revoke the key and the token dies with it.
Claude Desktop and Claude Code through the Agentu Bridge
The local option is the Agentu Bridge on your computer: it runs as a local MCP server over stdio (agentu-bridge mcp), decrypts on this computer and hands the app only the few memories that match a question. The keys stay with you. There is no npm package to install. In build The packaged Bridge for Mac is in build; until it ships, the Bridge is built from the repository.
One click. agentu-bridge connect claude-desktop writes the entry below into claude_desktop_config.json (~/Library/Application Support/Claude/ on Mac, %APPDATA%\Claude\ on Windows, ~/.config/Claude/ on Linux); then restart Claude Desktop. Manual: Settings → Developer → Edit Config, paste the entry with your real paths (which node and the Bridge's dist/agentu-bridge.mjs), save, restart.
{
"mcpServers": {
"agentu": {
"command": "/path/to/node",
"args": ["/path/to/agentu-bridge.mjs", "mcp"]
}
}
}
Claude Code. agentu-bridge connect claude-code runs this for you (--scope user so it applies in every folder). Manual: the same command; claude mcp list shows it, claude mcp remove --scope user agentu removes it.
claude mcp add --scope user --transport stdio agentu -- /path/to/node /path/to/agentu-bridge.mjs mcp
Prefer the hosted link instead of the Bridge? Claude Desktop takes the custom connector exactly as claude.ai does (first tab); for Claude Code use the --transport http line in the next tab. The Bridge only ever writes the agentu entry in each file, keeps a .bak-<timestamp> copy next to it, and agentu-bridge connect --remove <app> takes the entry out again.
ChatGPT connectors
- Open Settings → Connectors → Create (custom connectors require developer mode on Plus, Pro, Business or Enterprise plans).
- Name: Agentu Memory. URL:
https://memory.agentu.com/mcp. Authentication: OAuth. - ChatGPT opens Agentu's consent page. Paste a scoped key and allow.
- Enable the connector in a chat. Ask ChatGPT to remember something, then ask Claude about it — that is the whole point.
Codex, Claude Code, Cursor and VS Code
These apps sign in through a loopback callback on your computer. In build Agentu's sign-in for loopback callbacks is being fixed first, with a regression test in CI; each app is marked live here when the connection, the tool list, a read and a write all pass.
- Codex (CLI, desktop app and IDE extension share one file,
~/.codex/config.toml;agentu-bridge connect codexwrites it for you), thencodex mcp login agentuopens the Agentu approval screen. In the Codex app: Settings → MCP servers → Add server, nameagentu, URLhttps://memory.agentu.com/mcp.
codex mcp add agentu --url https://memory.agentu.com/mcp
- Claude Code with the hosted link (
--scope userapplies it in every folder;/mcpinside Claude Code signs in). The local path through the Bridge is in the previous tab.
claude mcp add --scope user --transport http agentu https://memory.agentu.com/mcp
- Cursor: open the install link below, or Settings → Tools & MCP → Add Custom MCP and paste
{ "url": "https://memory.agentu.com/mcp" }as theagentuentry in~/.cursor/mcp.json.agentu-bridge connect cursordoes the same and prints the link.
cursor://anysphere.cursor-deeplink/mcp/install?name=agentu&config=eyJ1cmwiOiJodHRwczovL21lbW9yeS5hZ2VudHUuY29tL21jcCJ9
- VS Code: open the install link below, or Command Palette → MCP: Add Server → HTTP →
https://memory.agentu.com/mcp→ nameagentu.agentu-bridge connect vscodewrites the entry into your usermcp.jsonand prints the link.
vscode:mcp/install?%7B%22name%22%3A%22agentu%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmemory.agentu.com%2Fmcp%22%7D
OpenAI Responses API (remote MCP tool)
For your own agents and products. Give the tool a key scoped to exactly the categories it needs.
{
"model": "gpt-5",
"tools": [{
"type": "mcp",
"server_label": "agentu_memory",
"server_url": "https://memory.agentu.com/mcp",
"headers": { "Authorization": "Bearer agk_live_…" },
"require_approval": "never"
}],
"input": "What did I decide about the board meeting?"
}
Perplexity custom connector
- On a Pro, Max or Enterprise plan open Settings → Connectors → Add custom connector.
- Name: Agentu Memory. URL:
https://memory.agentu.com/mcp. Authentication: OAuth (or an API key if your plan offers it: paste a scoped key). - Approve on Agentu's consent page. Enterprise admins can share the connector organisation-wide.
Gemini app and Gemini Enterprise
- Gemini app: Settings → Connected apps → Add custom app and paste
https://memory.agentu.com/mcp; authorise on Agentu's consent page. At launch Google limits custom apps to personal Google accounts, United States, English, 18+, with the activity setting on. - Gemini Enterprise: an administrator adds a custom MCP server (streamable HTTP) with the same URL and OAuth; the organisation policy must allow custom servers.
- Gemini API: pass
https://memory.agentu.com/mcpas anmcp_servertool with your key in the headers.
Any MCP client
Remote: Streamable HTTP at https://memory.agentu.com/mcp with OAuth 2.1 (discovery documents are published; Authorization: Bearer <key> for your own agents). Local: the Agentu Bridge over stdio, agentu-bridge mcp, with the keys on your computer. The server announces itself as Agentu Memory and exposes seven tools; every one takes an optional project (a name or id from list_projects), and without it uses the project this connection was given.
| Tool | Does | Annotations |
|---|---|---|
recall | Find the memories relevant to a question. query is a few words (names, topics); only the best matches come back, 5 by default and at most 12. Optional category: about-me, family, preferences, work, home, health, money, files, other. | Recall memories; read-only |
remember | Save one fact or preference the user wants kept, in their own words where possible. Optional category as above. | Remember; writes, not destructive |
remember_many | Move many memories into Agentu at once (for example everything the app already knows about the user). One short fact per item, at most 100. | Remember many; writes, not destructive |
remember_file | Record where a file or document lives and who owns it: name, location, system (own computer, own phone, server, Google Drive, iCloud Drive, OneDrive, Dropbox, SharePoint, S3 or other) and owner. Saved in Files & documents. | Remember where a file is; writes, not destructive |
find_file | Where is a file, and whose is it? query is a file name, a place, a system or an owner; returns the best-matching file records. | Find a file; read-only |
list_categories | Which memory categories this app may see, how many memories each holds, and whether it may save. | What can you see?; read-only |
list_projects | The user's projects this app can use, with memory counts in the shared categories. Sovereign (end-to-end encrypted) projects appear by name only; they open in the Agentu app or extension. | List projects; read-only |
Only the categories the user allowed for this app are visible, and only connected projects are reachable; a reviewer's project is read-only. Every read and write is written to the user's activity log.
One key per connection
Scope narrowly
Create keys with POST /v1/keys and give each model only the categories it needs. A key that cannot see Health cannot leak it.
Revoke freely
Stop trusting an app? Revoke its key. Its OAuth tokens and connections stop at once; nothing else changes.
Watch provenance
Every entry carries source.app and source.model. The audit log shows key activity — never content.