← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

Dimensiondeja-vuOne local memory shared by twenty-five coding agents, built from the session history already on disk.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS72 / 100 · B79 / 100 · B
Reliability11 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation18 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers who run several coding agents (Claude Code, Codex, Cursor, Copilot CLI, OpenClaw, opencode, Gemini CLI, Qwen Code, Kimi Code, Zed and more) and want them to share one history
  • Users who want memory to stay entirely local, with no LLM or embedding key required for default search
  • Engineers who need to reach back into months-old sessions to reuse prior fixes and decisions
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Users looking for a hosted or cloud knowledge base rather than local session history
  • Users unwilling to send (redacted, truncated) indexed text to a remote embedding endpoint, unless they configure a local Ollama or LM Studio runtime
  • Organizations that need a managed, multi-tenant, centrally administered memory service
  • Users expecting semantic recall with zero configuration, since it requires setting DEJA_EMBED_URL and related variables explicitly
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Reads the session-history directories of the agents on this machine (for example Claude Code's `~/.claude/projects`, Codex's `~/.codex/sessions`, Cursor's state.vscdb)
  • Writes a local inverted index and vector sidecar (.vectors.bin) under `~/.cache/deja`
  • `deja install` writes user-level guidance files (or a marked block inside them) for each harness it detects; `--no-guidance` opts out
  • Some harness parsers rely on local tooling: Cursor, Grok Build, Hermes, opencode, Crush and Zed need sqlite3; DeepSeek Harness and Zed need zstd
  • Network access is used only by `deja update`, `deja sync ssh`, and the version check in `deja doctor`; a remote endpoint receives redacted indexed text only after DEJA_EMBED_URL is configured
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Redaction is pattern matching, not secret detection: a shape it does not recognize can pass through into digests, share output or sync exports
  • Secrets already present in the original harness files stay in those files; deja-vu does not modify the sources
  • With a remote embedding endpoint configured, redacted indexed text (truncated to about 2k characters) leaves the machine; Ollama or LM Studio keeps embedding local
  • `deja forget` removes sessions from a rebuilt index and writes tombstones, but does not delete the underlying harness files
  • Session formats vary per harness and can change across versions, affecting parser completeness
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Code, Codex, Cursor, GitHub Copilot CLI, VS Code Copilot Chat, Gemini CLI, Qwen Code, OpenCode, Zed, Cline, Goose, Kimi Code, OpenClaw, Roo Code, Continue, Crush, aiderClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools10