linksee-memory

Linksee Memory MCP Server

Linksee Memory gives developers shared, local SQLite memory across coding assistants, including Claude Code, Cursor, Codex, and Gemini CLI. Its tools retain context, track decision drift, revisit unresolved proposals, and cache file reads.

Server facts

linksee-memory MCP Server

Project

License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
15
Last commit
Data as of

Tags

  • Cursor
  • Gemini Cli
  • Local First
  • Sqlite
  • claude code
  • cross agent
  • drift detection
  • memory

Overview

Coding work that moves between assistants can retain a common history through Linksee Memory’s local SQLite store. The remember tool creates, revises, or deletes records organized into six layers: goal, context, emotion, implementation, caveat, and learning. Caveats receive protection against automatic forgetting. With recall, agents can search stored knowledge, inspect a file’s editing history with intent context, or retrieve an entity overview. File reading has a separate workflow: read_smart supplies content and chunk metadata initially, then uses AST-aware caching to return changed chunks on subsequent reads.

Decision tracking starts with declare_anchor, which records explicitly stated human decisions and constraints rather than inferring them from patterns. drift_status reports alignment and unresolved divergence, while check_decision exposes an anchor’s premises and pending actions. where_am_i connects the current topic or recently edited files to related map nodes and affected dependencies. Through resolve_drift, users can record fixes, changed intent, deferred issues, or enforcement adjustments; Claude Code hooks also support resurfacing locked decisions before actions. For unfinished discussions, flag_proposals captures unanswered options. dream presents those proposals alongside project direction for evaluation, and resolve_proposal records whether each should remain visible for a human decision or be dismissed.

linksee-memory setup notes

  • linksee-memory records stdio only; confirm a network transport upstream before planning remote access.
  • linksee-memory has no recorded license; confirm reuse terms in its repository.

Related MCP servers