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.

DimensionPMB AILocal-first persistent memory for AI coding agents.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS63 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers using Claude Code, Cursor, or Codex
  • Users prioritizing privacy and local data control
  • Teams needing persistent memory without cloud dependency
  • 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 requiring online collaboration or cloud sync
  • Users without local disk space or needing real-time sync across devices
  • Users wanting zero configuration and avoiding command-line operations
  • 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 local filesystem (for indexing project, PDFs, etc.)
  • Write to local SQLite database and LanceDB indexes
  • Execute CLI commands (pmb)
  • Optional network access (e.g., when using Ollama or OpenAI for summarization)
  • 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
  • Local data loss risk if not backed up
  • Indexing large projects may consume disk space
  • Data is not encrypted by default; secrets are auto-redacted
  • Requires command-line familiarity
  • 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, Cursor, Codex, Windsurf, Zed, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools130