Linksee Memory
Hand a project over with the reasons attached.
Connector by michielinksee · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying Linksee Memory?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/michielinksee-linksee-memory
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 26, 2026.
- Tools
- 4 read · 3 write · 0 delete · 4 not yet classified
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Node.js package
Tools by what they do 11
Read from the source code; the running server may list different tools.
Read 4 · Look things up without changing anything.
check_decisiondrift_statusread_smartrecall
Write 3 · Create, change, send or run things.
flag_proposalsresolve_driftresolve_proposal
Not yet classified 4 · We could not tell from the name and description.
declare_anchordreamrememberwhere_am_i
Network hosts it talks to 5
docs.anthropic.com· found in codedocs.linksee.app· found in codegithub.com· found in codeglama.ai· found in codelinksee-site.vercel.app· found in code
Files it touches
- Your home directory (~)
C:\\Users\\HP\\KanseiLINK\\kansei-link-mcp- Any path the agent passes to its tools
Tools (11)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
check_decisionDeep-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 first • When reviewing premises of a decision ("is this still true?")
declare_anchorDeclare 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 approach A") • When a constraint is established ("never do X") • When a commitment is made ("we ship weekly") • When the user says "anchor this" / "record this decision"
dreamDreaming Memory — consolidate orphaned proposals against the North Star. Returns the project's North Star (direction/goals/ICP/phase) alongside unresolved proposals that agents flagged during conversations. YOUR job as the evaluating agent is to decide: • surface — genuinely important unresolved fork point given the current direction • dismiss — outdated, already implicitly resolved, or irrelevant to current goals Think like a General Doctor doing triage: the North Star is the patient's chart, each proposal is a symptom. Not every symptom needs treatment. WHEN TO CALL: • At session start t…
drift_statusCheck 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 → Decision Cards (decision journal format) • constraint → Rules (pass/fail checklist) • commitment → Heartbeats (cadence monitoring) • source_of_truth → Reference (stable anchors) WHEN TO CALL: • At se…
flag_proposalsRecord orphaned proposals — options you presented that the user never addressed. Conversations are tree-shaped but experienced linearly. When you present 3 options and the user engages with only 1, the other 2 become "orphaned proposals" — unresolved decision branches that both you and the user lose track of. WHEN TO CALL: • When you notice the user engaged with only some of the options you presented • When the conversation shifted topic and earlier proposals were never resolved • At session end, review what you proposed vs what was addressed • When the user says "what else did we discuss?" …
read_smartToken-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 this over Read.
recallYour 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 mentions "before" / "前に" / "last time" / "remember when" • When an error occurs — check if you've seen it before • When making a decision — check for prior decisions on the same topic THREE MODES (a…
rememberPersist 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" • When something new is learned → layer: "learning" • When the user says "remember this" / "覚えておいて" • After completing a task or receiving user approval MODES: • Create (default): content is the onl…
resolve_driftRecord 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 dismissed AND the gate stops firing on it (hit_term: just that word; gate:false: close the edges but keep the gate watching) • harden — "re-injected but still violated, enforce it" → card_policy.gate_mode=h…
resolve_proposalRecord your evaluation verdict for an orphaned proposal after dreaming. Call this after `dream` for each candidate you evaluated against the North Star. • surface — Keep visible on dashboard for human decision • dismiss — Remove from dashboard (outdated/irrelevant/implicitly resolved) Always reference the North Star criteria in your rationale.
where_am_iLocate 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 (linked anchor), if any. Three ways to call: • NO ARGS → auto-locates from the files you JUST edited this session (the zero-effort re-anchor — call it freely as you work). • query: "<topic>" → lexi…
Signals
- Stars
- 15
- Forks
- 4
- Open issues
- 0
- Last commit
- Sep 9, 2026 (1 month ago)
- Last release
- Sep 8, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.michielinksee/linksee-memory- Version
- 0.15.2
- Auth
- No auth
- Packages
- npm linksee-memory
- License
- MIT
- Repository
- github.com/michielinksee/linksee-memory
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from michielinksee
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get Linksee Memory running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
Linksee Memory MCP server. Agent Mart. https://agentmart.dev/connectors/michielinksee-linksee-memory (last updated 2026-10-24)