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.

DimensionAsk GeminiBridge Claude with Gemini CLI for AI-to-AI review and second opinionsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS55 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Large-context, whole-codebase code review
  • Teams that already hold enterprise Gemini Code Assist seats
  • Developers who want to consult Gemini inside clients like Claude or Codex
  • File-scoped prompts using @ syntax for precise references
  • 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 with only free, Google AI Pro, or Ultra accounts (Gemini CLI is enterprise-gated since 2026-06-18)
  • Environments where the Gemini CLI cannot be installed or authenticated
  • Users expecting zero extra CLI setup
  • 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 locally installed and authenticated Gemini CLI
  • Communicates with the local MCP client over stdio
  • Reads referenced code file contents included in prompts and sends them to Gemini
  • 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
  • Code content leaves the machine for Gemini's service; assess data-transfer risk for sensitive code
  • Non-enterprise accounts cannot use Gemini CLI and may only receive guidance instead of results
  • The default 5-minute timeout may be exceeded on large whole-repo requests; adjust GMCPT_TIMEOUT_MS
  • Unofficial third-party project, not supported by Google or Anthropic
  • 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 Code, Claude Desktop, Cursor, Codex, PiClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools50