Connect Claude Code, Codex or Cursor to Atris Memory in Three Steps
Atris Memory is one memory about a person that every app and agent they use can share. It is a folder of plain pages: who they are, what matters now, a page per day, a wiki, their files, and a notebook for each agent that works for them.
An agent connects in three steps and about two minutes.
Step one: make a key
npm install -g atris
atris login
atris api-key create memory
The last command prints a key that starts with atris_. Keep it somewhere
safe. You can revoke it any time with atris api-key revoke <id>.
Step two: add the connection
The address is https://api.atris.ai/mcp. Put your key where atris_YOUR_KEY
is.
Claude Code:
claude mcp add --transport http atris https://api.atris.ai/mcp --header "Authorization: Bearer atris_YOUR_KEY"
Codex, with ATRIS_API_KEY=atris_YOUR_KEY set where Codex runs:
codex mcp add atris --url https://api.atris.ai/mcp --bearer-token-env-var ATRIS_API_KEY
Cursor, in ~/.cursor/mcp.json:
{"mcpServers":{"atris":{"type":"http","url":"https://api.atris.ai/mcp","headers":{"Authorization":"Bearer atris_YOUR_KEY"}}}}
Any other app that speaks MCP over HTTP works the same way: the address above and the key as a bearer token.
Step three: tell the agent to use it
Run this in your project and it writes a short rules block into the file your agent reads, and keeps it current:
atris memory agents --write AGENTS.md
Use CLAUDE.md or .cursorrules in place of AGENTS.md if that is the file
your agent reads. Run atris memory agents alone to print the block and paste
it yourself.
Check it works
Ask your agent: "What do you know about me from Atris?" It should call
my_memory and answer from your pages.
From the terminal, the same memory:
atris memory show
atris memory search "rent|lease"
atris memory ls
What the agent can do
Eleven tools, all free to call.
| Tool | What it does |
|---|---|
my_memory | Who the person is and what matters now. Read it before helping. |
remember | Save one short lasting fact when they say remember, note or save. |
memory_search | Find lines by word across the whole folder. Put every spelling in one search. |
memory_read | Open one page as numbered lines. |
memory_ls | List a folder. |
memory_write | Save a wiki page, or something made for the person under files/. |
memory_delete | Delete a wiki page or a file. |
memory_link | Get a download link for a photo, PDF or recording. It lasts 10 minutes. |
memory_log | Add one line to the agent's own day page. |
memory_lesson | Keep a lesson, only when a score went up. |
memory_usage | File space used and what the plan gives. |
How the folder is laid out
MAP.md what lives where; read it first
about.md who they are
now.md what matters now
board.md their goal and deadline
logs/YYYY/YYYY-MM-DD.md what they said each day
wiki/ topic pages
wiki/index.md one line per wiki page
files/ their uploads and what agents made
files/index.md one line per file
team/<agent>/ each agent's own notebook
team/<agent>/logs/YYYY/YYYY-MM-DD.md what that agent did each day
Five rules worth knowing
One. Made things get a dated name. When an agent saves
files/trip-plan.md, it is stored as files/2026-11-10-trip-plan.md. The
reply gives the real path, so tell the person that one. A name that already
has a date keeps it.
Two. Read the index before listing a folder. files/index.md and
wiki/index.md hold one line per item: what it is, who wrote it, the day.
They update in the same step as every save and delete.
Three. The indexes are kept for you. Writing or deleting one by hand is refused. Save or delete the page and its line follows.
Four. Know where each thing goes. A fact the person tells you goes through
remember, never a page write. What you worked out on a topic goes in
wiki/. Something you made for them goes in files/. Your own notes go in
your notebook under team/<agent>/.
Five. Give a save a second before you search for it. A search sent in the same instant as a save can miss the new page. One second later it is there.
Questions
Does it cost anything? The memory tools are free to call. File space
depends on the plan; memory_usage shows what is used.
Who can read it? The person, and the apps and agents they gave a key to. Revoke a key and its access stops.
Can several agents share one memory? Yes. That is the point. Each keeps its own notebook, and all of them read the same pages about the person.
Where do I see my memory? At atris.ai/dashboard/memory, or with
atris memory ls.