M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionRemem MCP ServerLocal-first persistent memory for coding agents: automatic capture, distillation, and recall.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS66 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation18 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers using Claude Code or Codex CLI long-term
  • Teams needing searchable, auditable, project-scoped memory
  • Users who want data to stay local (SQLite/SQLCipher)
  • 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
  • Cursor users (v1 lacks session-init injection and automatic capture)
  • Anyone needing hosted or team-shared memory services
  • Users wanting a zero-install, no-local-binary solution
  • 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/writes the ~/.remem/ data directory and encrypted database
  • Modifies Claude Code / Codex / Cursor config files to register hooks and the MCP server
  • Calls the configured LLM API in the background for summarization and distillation (incur token costs)
  • Optional local REST API binds only to 127.0.0.1 and requires Bearer token auth
  • 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
  • Background memory summarization via external LLMs incurs ongoing token costs
  • Cursor integration is v1: automatic capture and session-init are not enabled, and config updates are not cross-file atomic
  • Stores project and user context; accidental secret-like content relies on built-in redaction scans and suppression tooling
  • Command enforcement (block mode) is Claude Code only; explicitly unsupported on Codex
  • 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, OpenAI Codex CLI, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools60