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.

DimensionClaude MemPersistent cross-session memory for Claude Code and other agentsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS50 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions5 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience10 / 2015 / 20
Best for
  • Developers working on long-running projects with Claude Code (or other supported agents) who want memory to persist across sessions
  • Teams that want automatic summarization of agent tool activity instead of manual note-taking
  • 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
  • Privacy-sensitive workflows where agent activity shouldn't be logged/stored by default without manually excluding content via <private> tags
  • One-off, single-session tasks that don't need cross-session context
  • Environments where installing a background worker service (Bun) and a Python package manager (uv) is not permitted
  • 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
  • Local file system read/write access for session logs, the SQLite database, and configuration (~/.claude-mem)
  • Ability to run and manage a background worker process (Bun) and a Python package manager (uv)
  • Network access for AI-based summarization/compression calls and optional cloud sync to cmem.ai
  • Access to Claude Code (or other agent) lifecycle hooks and tool-use transcripts in order to capture observations
  • 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
  • Captures and stores all tool-use activity from agent sessions by default; sensitive content must be manually excluded using <private> tags
  • Runs a local HTTP worker service with a web viewer, which exposes stored memory data on the local machine/network
  • Optional cloud sync transmits memory data to a third-party service (cmem.ai)
  • Auto-installs additional runtimes (Bun, uv) when missing, widening the trust/supply-chain surface
  • The project is associated with a third-party cryptocurrency token (CMEM) that is not part of the core software — a separate financial-risk consideration, not evidence of malicious code
  • 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, OpenCode, OpenClaw, Codex, Gemini, GitHub CopilotClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools30