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.

DimensionGemini CLIAn open-source AI agent for Gemini in your terminalMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS58 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance16 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers who work primarily in the command line
  • Individual developers and teams needing code understanding, generation, and automation
  • Users who want to connect custom MCP tools to Gemini CLI
  • 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 looking for a documented MCP tool catalog
  • Users needing a standalone MCP server to deploy and connect directly
  • Environments that do not permit terminal, file, or shell capabilities
  • 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
  • Gemini authentication through a Google account, Gemini API key, or Vertex AI configuration
  • File and shell access when the corresponding built-in tools are used
  • Network access for Google Search grounding and web fetching
  • GOOGLE_CLOUD_PROJECT may be required for paid organizational Code Assist licenses
  • 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
  • File operations and shell commands can affect the project or runtime environment; sandboxing and trusted-folder controls should be reviewed
  • Preview and nightly channels may contain regressions or outstanding issues
  • API keys, Google accounts, and cloud project configuration require protection
  • 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, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools00