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 Antigravity MCP ServerBridge Claude with Google's Antigravity CLI for a second model's reviewMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS59 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions11 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Users who already have a Google AI Pro/Ultra subscription and the agy CLI installed
  • Developers who want an independent review from a different vendor's model
  • One-shot, quota-backed second-opinion calls without metered API billing
  • 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
  • Environments without the Antigravity CLI (agy) installed and authenticated
  • Workflows needing multi-turn sessions or session resume (this server is one-shot)
  • Production-critical flows requiring stable, non-experimental guarantees
  • Users who cannot send code to Google models (use the Ollama server for fully local runs)
  • 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
  • Spawn the agy CLI (Antigravity CLI) process on the host machine
  • Use the locally stored Google AI Pro/Ultra credentials and subscription quota
  • Read code and file context passed in as prompt content (sandbox on by default; reading directories via --add-dir may require setting ASK_ANTIGRAVITY_SANDBOX=0)
  • Write local logs and npm cache
  • 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
  • Reviewed code is sent to Google's Antigravity service, which may expose sensitive information
  • Sandbox is on by default; setting ASK_ANTIGRAVITY_SANDBOX=0 to read context reduces that isolation
  • The server is experimental and one-shot, and behavior or quota may change upstream
  • Long runs may time out (default 5 minutes), especially with large context reads
  • Subscription quota may be consumed or rate-limited
  • It is an unofficial third-party tool with no affiliation to 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, Cursor, Codex, Claude DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools10