MCP Tools DirectoryAbout this integration
Hand a project over with the reasons attached. Local-first cross-agent memory MCP + drift detection.
- Transport
- stdio
- Authentication
- none
- Initial setup
- none
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.15.2
- Package
- linksee-memory
- Last compatibility test
- Not independently tested
Connect your agent
linksee-memoryPublisher documentation reviewed; package not executed. The documented local stdio path needs no account or API key; optional telemetry is separate and off by default.
Capabilities: Store project decisions, Recall cross-session context, Detect project drift
Connected profiles
Additional details
io.github.michielinksee/linksee-memory
Source ↗ · Checked 2026-09-170.15.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17linksee-memory
Source ↗ · Checked 2026-09-190.16.1
Source ↗ · Checked 2026-09-19| Feature | Detail | |---|---| | **3-tool unified surface** | 8 tools → 3: `remember` (create + update + delete), `recall` (search + file history + overview), `read_smart` (token-saving reads). Fewer tools = better cross-LLM consistency. Follows Context7's proven pattern. | | **Auto-consolidate** | Consolidation runs automatically on server startup (non-blocking, 7-day threshold). No manual `consolidate()` calls needed. | | **Deprecation guidance** | Old tool names (`forget`, `recall_file`, etc.
Source ↗ · Checked 2026-09-19**Is there a local-first, self-hosted alternative to Mem0 for agent memory?** Yes. No account, no API key, no cloud — one local file, MIT licensed. `npx -y linksee-memory setup` and it's on.
Source ↗ · Checked 2026-09-19npx -y linksee-memory setup
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19