Cairn
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Cairnsearch my old conversations for how we fixed the auth bug"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Cairn
Your Claude Code conversations, on every account. Saved before Claude deletes them, and shared with every account you sign into.
π¬π§ English Β· π«π· FranΓ§ais Β· πΉπ· TΓΌrkΓ§e Β· π¦πΏ AzΙrbaycanca
π― Why
You signed into a different Claude account and your conversations vanished.
They are not gone. They are on your disk, exactly where they were. Claude keeps a separate list for each account, and after you sign in somewhere else it is reading the wrong list.
There is a second problem, quieter and worse: Claude Code deletes conversations after 30 days. By default, without telling you. Most people find out when something they wanted is already gone.
Cairn fixes both, then gets out of the way.
Related MCP server: cursor-history-mcp
π Install
πͺ Windows β no terminal needed
1 | β¬ Download |
2 | Double-click it. |
3 | Press |
4 | Quit Claude completely, then open it again. |
Done. Your conversations are back in the sidebar.
Run it once more and press 3 to turn on automatic sync, so this was the
last time you had to do anything.
π macOS / π§ Linux
npx github:veax-project/claude-cairnSame screen, same steps.
β οΈ Then quit and reopen Claude
Claude reads its list of conversations once, at startup. Cairn can add to that list, but Claude will not notice until the next launch. This is the #1 reason people think it did not work.
π¦ It needs Node.js
Most developers already have it. If you do not, the window tells you so and points you there β install the version marked LTS, then run it again.
β¨ What it does
πΎ Saves them. Every conversation is copied somewhere Claude does not delete from. That copy is yours, and nothing removes it.
π Shares them. Every account on your computer gets every conversation β in both directions. Start something on one account, switch to another, it is there. Go back, and the work you did in between is there too.
ποΈ Watches. Turn on automatic sync and both happen every ten minutes, starting with your computer. You never think about it again.
π Lets Claude search it. From any account, including one you made five minutes ago.
β©οΈ Undoes itself. One command removes exactly what it wrote, and nothing else.
π Let Claude search your own history
npx github:veax-project/claude-cairn install-mcpRestart Claude, then ask it things like:
search my old conversations for how we fixed the auth bug
This works on any account, including a brand-new one. That is the whole point: the connection belongs to your computer, not to an account.
π§― Troubleshooting
Symptom | Cause | Fix |
π Nothing came back | Claude was already open | Quit it completely and reopen β it only reads the list at startup |
πͺ The window closed instantly | Node.js is missing | Install it from nodejs.org, pick LTS, run the file again |
π€· A conversation is still missing | It belonged to a different project | The sidebar is filtered by project β open that project's folder |
π’ Accounts show as codes | Nothing on your disk says who they were | Press |
π± It made things worse | β |
|
π Nothing at all on a Mac | Never tested there | Tell us what happened β that is the only way it gets fixed |
π‘οΈ Where your data goes
Nowhere. Cairn copies files from one folder on your computer to another folder on your computer.
π« Zero dependencies. The
dependenciesblock inpackage.jsonis empty.π« Zero network calls. No telemetry, no update check, no analytics. Turn off your wifi and every command still works β the easiest way to check for yourself.
π The MCP server talks to Claude over standard input and output. It opens no socket.
ποΈ Nothing is ever deleted from your backup. Not even by Cairn.
β©οΈ
undoremoves only what it wrote, recognised by size and timestamp β anything Claude has touched since is left alone.
Around 3000 lines of plain JavaScript, no build step, no bundler. Eleven files
in src/, and you can read any of them.
The launcher is a 90-line .cmd that checks for Node, downloads the release
archive, and runs it. It is pure ASCII and does nothing else.
π Commands
Command | What it does |
| Opens the screen at the top of this page |
| Save everything, then give every account everything |
| Keep doing that, every 10 minutes, from startup |
| What is here, what is hidden, what is at risk |
| Remove exactly what the last sync wrote |
| Search across every account |
| Let Claude search the archive itself |
| Write every conversation out as Markdown |
| Bundle conversations into one file to attach to a chat |
Your backup lives in ~/ClaudeCairn. Move it with --vault <folder> or the
CAIRN_VAULT environment variable.
π¬ How it works
Claude Code keeps two separate things, in two separate places:
~/.claude/projects/<project>/<id>.jsonl
the conversation itself
deleted once it is older than cleanupPeriodDays β 30 by default
<appData>/Claude/claude-code-sessions/<account>/<org>/local_*.json
the sidebar entry that lists it
one folder per account, which is why switching hides everythingCairn copies the first somewhere safe, and writes the second under every account it finds. Conversations are only ever appended to, so a file that has not grown is skipped. Nothing is ever removed from the backup β a conversation Claude has already deleted stays, because that copy is now the only one in existence.
Claude checks each sidebar entry against a strict shape before it will list it, and silently drops anything that does not match. Cairn builds them from the shape observed in real files: timestamps as numbers rather than text, no extra fields, and none of the placeholder values that occasionally appear in transcripts.
The search index is SQLite full-text search, using the copy that ships inside Node. That is why there are no dependencies.
β οΈ Beta
A first release. Verified end to end on Windows: 23 conversations that had been invisible for weeks came back into the sidebar after a restart, and every entry Cairn wrote was accepted.
21 automated tests, including one that replays the interface onto a simulated terminal at seven window sizes to catch layout faults.
β Proven | Windows |
β Never run | macOS, Linux β the code is written and reviewed, nothing more |
β Impossible | Conversations Claude deleted before your first backup. Nothing brings those back. |
β Out of scope | Regular claude.ai chats. Those live on Anthropic's servers and cannot be moved between accounts β a limit of the product, not of this tool. |
Open an issue β especially if you are on a Mac.
GPL-3.0 Β· Built because switching accounts should not cost you your work.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server that lets you search your Claude Code conversation history to find past solutions, track file changes, and learn from previous work.8153177MIT
- AlicenseAqualityBmaintenanceMCP server for browsing, searching, exporting, and backing up your Cursor AI chat history directly into Claude via natural language.814032MIT
- AlicenseAqualityCmaintenanceAn MCP server that lets Claude Code recall the context of past conversations from any project on demand.5492MIT
- AlicenseAqualityDmaintenanceAn MCP server that indexes Claude Code conversation history into SQLite, enabling full-text search across past sessions for context recovery and cross-agent observability.103MIT
Related MCP Connectors
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/veax-project/claude-cairn'
If you have feedback or need assistance with the MCP directory API, please join our Discord server