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.

DimensionNauroGive your agents the context code leaves out.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS58 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Long-term projects where project context decays across sessions, tools, and handoffs
  • Pairing with AI coding agents like Claude Code, Codex, or Cursor to reduce redundant questions and context loss
  • Teams that value local data ownership and human-approved decision records
  • 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
  • Small repositories: if a reliable AGENTS.md or CLAUDE.md keeps agents oriented, Nauro may be overkill
  • CI/CD pipelines requiring strict enforcement on every change—Nauro's retrieval is advisory and never blocks
  • Users wanting fully automatic decision logging without human approval gates
  • 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
  • The local record is plain Markdown that you own; local use needs no account and sends no analytics
  • Nauro can read project files (e.g., README, code) to assess decision rationale but writes only after your explicit approval
  • Installation may add skill files and workflow agents (e.g., nauro-ship-task) if requested
  • Explicit overwrite via `nauro sync` is the only controlled override path, preserving manually managed files
  • 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
  • Unmanaged AGENTS.md may be overwritten—Nauro preserves it during adoption; `nauro sync` is the sole explicit overwrite path with a `# Manual` section protecting it
  • As an MCP server, it uses stdio; any client with access to the MCP can read the local record content
  • Nauro does not enforce decisions on agents; it is advisory, so agents might ignore stored judgment
  • 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 DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools10