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.

DimensionMemory Bank MCP ServerA remote memory bank management MCP server with multi-project isolation.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS45 / 100 · D79 / 100 · B
Reliability6 / 2012 / 20
Security and permissions7 / 2018 / 20
Maintenance9 / 2016 / 20
Documentation11 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers using MCP clients like Cline, Claude Code, or Cursor
  • Teams that need to manage memory banks for multiple projects centrally
  • Advanced users wanting to integrate memory banks via MCP
  • 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
  • Simple single-project scenarios that do not need multi-project isolation
  • Environments without Node.js or network access
  • Features requiring real-time synchronization or collaborative editing
  • 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
  • Read and write files under the specified directory (MEMORY_BANK_ROOT)
  • Create and update memory bank files
  • List projects and files within projects
  • 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
  • Misconfiguration of MEMORY_BANK_ROOT may lead to accessing unintended directories
  • Unauthorized access could expose sensitive information
  • Dependency on Node.js runtime and network
  • Third-party server may not have undergone official security audit
  • 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 Desktop, Claude Code, Cline, Roo Code, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools50