← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionAsk LLM MCP ServerGive your AI coding assistant a second opinion from a different modelMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS59 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who have at least one supported provider CLI installed and authenticated, or the relevant API keys configured
  • Teams that want cross-model code review and plan debate inside their coding workflow
  • Users who need private or offline review via Ollama
  • Users of MCP clients such as Claude Code, Codex CLI, Cursor, and Claude Desktop
  • 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 any provider CLI installed or keys configured (the server does not supply model access itself)
  • Environments that cannot install Node.js 20+ or are not Linux/macOS
  • Users expecting a fully hosted, zero-config, or officially supported product
  • Scenarios where outbound data transfer is strictly forbidden and no local provider such as Ollama is available
  • 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
  • Read local workspace files for context (e.g. Claude provider's Read/Glob/Grep-only access, Gemini's @ file syntax)
  • Launch and call installed provider CLIs locally (codex, claude, agy, gemini, agent, etc.)
  • Network access to call the xAI API (when using XAI_API_KEY) and the local Ollama service (default http://localhost:11434)
  • Read API keys from environment variables (e.g. XAI_API_KEY, CURSOR_API_KEY)
  • Cursor Agent runs in read-only ask mode and does not change force/trust/spend settings
  • 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 and prompts may be sent to external model providers, creating data-transfer exposure; choose Ollama when local privacy is required
  • Metered endpoints such as the xAI API incur real costs; ASK_GROK_MAX_OUTPUT_TOKENS only bounds spend, it does not make it free
  • Grok and Ollama never fall back to another model, so requests may fail outright
  • Gemini CLI has been enterprise-seat-only since 2026-06-18; non-enterprise accounts get guidance instead of output
  • Antigravity is experimental and one-shot, with limited reliability
  • Plugin workflows such as codex-pair can trigger repeated external calls and costs, requiring an explicit marker and consent
  • This is a third-party, unofficial tool with no affiliation with or endorsement by Anthropic, Google, OpenAI, or xAI
  • 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
Tools140