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.

DimensionPare JvmStructured Gradle & Maven build tool operations as typed JSON for AI agents.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS43 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation8 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • JVM projects using Gradle or Maven.
  • AI coding agents that need structured data directly.
  • Reducing token consumption from build tools.
  • 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
  • Projects that do not use JVM build tools.
  • Advanced build scenarios requiring non-standard CLI output.
  • Build operations that require interactive terminal or TTY.
  • 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
  • Ability to execute Gradle and Maven commands.
  • Read access to project files and build configurations.
  • Network access to download dependencies if needed.
  • Permissions to create, modify, and delete build artifacts and temporary 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
  • Executing build commands may modify project files (e.g., generated files, clean target directories).
  • Potential unintended build/test execution if commands are unrestricted.
  • Potential loss of build cache or unsaved work.
  • Risk from running in untrusted repositories; ensure project source is trusted.
  • 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, Cursor, VS Code, Windsurf, Cline, Roo Code, Codex, Gemini CLI, ZedClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00