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.

DimensionSonarQube MCP ServerSeamless integration of SonarQube code quality and security analysis into AI assistants.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS66 / 100 · C79 / 100 · B
Reliability10 / 2012 / 20
Security and permissions15 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Teams using SonarQube
  • Developers who want to integrate static analysis into AI workflows
  • Organizations needing automated code review and compliance checks
  • 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 without a SonarQube account or token
  • Personal projects that don't require code quality analysis
  • Users who want to use MCP without external dependencies
  • 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
  • Requires a SonarQube user token to access the API
  • May require organization key or server URL
  • Needs network access to the SonarQube instance when running in a container
  • Optional workspace mount to read 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
  • Token leakage: ensure tokens are stored securely and not hardcoded
  • Data privacy: code analysis may involve sensitive code; ensure secure connection
  • Resource consumption: large analyses may consume computational resources
  • Container security: use official images to avoid malicious code
  • 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, VS Code, Cursor, Zed, Windsurf, Gemini CLI, GitHub Copilot CLI, GitHub Copilot coding agent, Antigravity, Kiro, CodexClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools240