Linksee Memory MCP server

Read from the package source without running it. The installed server may list more.

• check_decision

  Deep-dive into a specific decision/anchor — its state, premises, drift edges, and pending candidates. Returns the full context for one truth-map node: what was decided, why, what reality says, whether it's drifting, and what actions are pending. WHEN TO CALL: • When the user asks about a specific decision ("what happened with X?") • Before resolving a drift signal — understand the full picture fir

• declare_anchor

  Declare a new decision, constraint, or prohibition as a truth-map anchor. Anchors are NORMATIVE claims: "we decided X", "Y is forbidden", "Z must always hold." The drift detector later checks these against committed reality. declare-don't-mine: anchors come ONLY from explicit human declaration, never from pattern extraction. WHEN TO CALL: • When the user makes a product decision ("let's go with ap

• dream

  Dreaming Memory — consolidate orphaned proposals against the North Star.

• drift_status

  Check what's drifting right now — the "Intent Datadog" for your product decisions. Returns a structured truth map showing which decisions/constraints/hypotheses are: 🔴 drift (unaccounted divergence from intent) 🟡 review (soft signal, awaiting human decision) ⚪ held (acknowledged, time-boxed, not forgotten) 🔵 aligned (reality matches intent) Nodes are classified into 4 species: • hypothesis → De

• flag_proposals

  Record orphaned proposals — options you presented that the user never addressed.

• read_smart

  Token-saving file reader with AST-aware diff caching. Use INSTEAD of the standard Read tool for ALL file reads — even first reads gain chunk metadata for future savings. • First read: full content + chunk metadata (enables future savings) • Re-read unchanged: ~50 tokens (99% savings) • Re-read modified: only changed chunks (50-90% savings) Especially effective for files >200 lines. Always prefer t

• recall

  Your persistent memory across all AI tools. CALL THIS BEFORE STARTING ANY TASK to check for past caveats (pain records), decisions, and learnings — prevents repeating mistakes across sessions. Typical usage: recall({ query: "keywords" }) for search, recall({ path: "file.ts" }) for file history, recall() for overview. WHEN TO CALL: • Before starting any new task or touching a file • When the user m

• remember

  Persist knowledge across sessions and AI tools (Claude, GPT, Cursor, Codex, Gemini). The only cross-agent memory that survives session boundaries. WHEN TO CALL: • The moment an error or failure occurs → layer: "caveat" (auto-protected, never forgotten) • When a decision is made or approved → content + anchor: {} (remembered AND enforced in one call) • When a goal is set or updated → layer: "goal"

• resolve_drift

  Record a resolution for a drifting anchor — the human feedback loop. 6 actions: • fix — "we fixed the code/reality to match intent" → state becomes aligned • supersede — "intent evolved, this is the new direction" → state becomes aligned • acknowledge — "we know, parking it for now" → state becomes held (with optional review date) • dismiss — "false positive, not actually drifting" → edges dismiss

• resolve_proposal

  Record your evaluation verdict for an orphaned proposal after dreaming.

• where_am_i

  Locate the current topic on the Current Truth Map and report "you are here" + blast radius — the per-turn re-anchor. Returns the matching Map node(s) + journey stage (discover → … → expand), the BLAST RADIUS (what becomes suspect if you change this — the must-stay-consistent-with / should-align-with / realizes dependents; e.g. editing the README implicates the LP), and the decision behind the node

• Code scan79 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 11 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Linksee Memory: common questions

Is Linksee Memory MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the Linksee Memory safety report

How do I install Linksee Memory?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Linksee Memory need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Linksee Memory maintained?

The last commit was 11 days ago (2026-09-09). The latest release is v0.15.2.

What can I use instead of Linksee Memory?

Servers from other publishers that do the same job: Agent Memory Os MCP server, ContextStream MCP Server and Google Surf MCP server. Compare all Linksee Memory alternatives.