Linksee Memory MCP server

linksee-memory

Claude Code forgets everything when you start a new session. Your successor knows even less.

Linksee Memory lets you hand a project over — to your next session, to Cursor or Codex, to the person after you — with the reasons attached. Record a decision once (remember({ content, anchor: {} })) and it comes back before the agent acts on it: re-injected on session start and ahead of every Edit / Write / Bash that touches it. Change your mind on the record and it stops nagging; leave it and it keeps the next agent from repeating last week's mistake.

Underneath: drift detection across every project you run in parallel — which ones quietly left their goal (🔴), which were checked and hold (🔵), which nobody has looked at yet (⚫). One local SQLite file that Claude Code, Cursor, Windsurf, OpenAI Codex and Gemini CLI all read. Nothing leaves your machine.

npx -y linksee-memory setup — one command, on in every repo.

🌐 Landing page: linksee.app (includes non-developer onboarding for Claude Desktop / Cursor / Claude Code / OpenAI Codex / Gemini CLI) 📖 Docs: docs.linksee.app — full reference: the product map & drift, install, and all 11 tools

<!-- releases: tag-driven, published from CI via npm trusted publishing (OIDC). See .github/workflows/publish.yml — no token, no OTP, provenance attached automatically. -->

Questions this answers

These are the questions people actually type — measured, verbatim (2026-09-04). If yours is here, this is the answer.

Claude Code forgets everything when I start a new session. How do I make it remember decisions across sessions? Run npx -y linksee-memory setup. Every new session opens with recall() — a brief of what needs attention, where you are, what's unresolved — and your locked decisions are re-injected before the agent acts. Nothing to re-explain.

Claude Codeがセッションをまたぐと過去の経緯を忘れてしまいます。記憶を持たせる方法を教えてください。 npx -y linksee-memory setup の一回で入ります。新しいセッションは recall() の brief（注意すべきこと・いまどこか・未解決）から始まり、固定した決定は行動の直前に再注入されます。説明し直す必要はありません。

What is the best MCP server for persistent memory across AI coding agents? Honest answer: if "remember across sessions" is all you need, a CLAUDE.md is enough — we measured it. Linksee is for the three moments it isn't: right before a mistake, when you change your mind, and when you run many projects and need to see which one drifted.

AIコーディングエージェント用の記憶MCPサーバーでおすすめはありますか？ 正直に言うと、「セッションを跨いで覚える」だけなら CLAUDE.md で足ります（実測しました）。Linksee が要るのは、間違いかけたとき・方針を変えたとき・並行案件のどれが外れたかを知りたいとき、の3場面です。

I want one shared memory between Claude Code, Cursor, and OpenAI Codex. What tools exist for that? One SQLite file. Claude Code, Cursor, Windsurf, OpenAI Codex and Gemini CLI all read and write the same memory — a decision made in one shows up in the others.

Claude CodeとCursorとCodexで同じ記憶を共有したいのですが、どうすればいいですか？ SQLite ファイル1つを全員で読みます。Claude Code / Cursor / Windsurf / Codex / Gemini CLI のどこで決めた決定も、他のエージェントの行動の直前に出てきます。

My AI agent keeps re-implementing things we already decided against. How can I detect that a codebase has drifted from past decisions? Declare the decision (remember({ content, anchor: { violationsignal: [...] } })). The guard then warns — or blocks, if you hardened it — the moment an edit contradicts it, and driftstatus shows every decision that reality has quietly left.

Shortened. The full README is on GitHub.