← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionDesktop CommanderSearch, update, manage files and run terminal commands with AIMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS54 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers who want AI assistants to directly control terminal and file system.
  • Users who need enhanced code editing, automation, and codebase exploration within MCP clients like Claude Desktop.
  • Scenarios requiring handling of complex file formats like Excel, PDF, DOCX.
  • 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 needing a fully sandboxed environment (unless using Docker installation).
  • Security-sensitive environments, as terminal commands can bypass directory restrictions.
  • Users who don't need terminal control and only basic file 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
  • Filesystem read/write permissions, including terminal commands that can access files outside allowedDirectories.
  • Ability to execute arbitrary terminal commands (subject to blockedCommands).
  • Manage processes (start, interact, terminate).
  • Access network to fetch URL content (read_file).
  • 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
  • Terminal commands can access files outside allowedDirectories, posing a security risk.
  • Command blocklist may be bypassed via symlinks, command substitution, or absolute paths.
  • Configuration changes should be made in a separate chat window to avoid accidental modification by Claude.
  • Potential risk to host system if not using Docker isolation.
  • 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, Windsurf, VS Code / GitHub Copilot, Cline, Roo Code, Claude Code, Trae, Kiro, Codex, JetBrains IDEs, Gemini CLI, Augment Code, Qwen CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools250