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.

DimensionKode CLIMulti-model terminal AI coding agent that acts as an MCP client to connect external tool serversMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS44 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions3 / 2018 / 20
Maintenance11 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers who want multi-model orchestration inside a terminal coding agent
  • Teams already using the AGENTS.md standard or migrating from similar terminal AI coding tools
  • Users who want to extend a coding agent's capabilities by connecting it, as an MCP client, to custom external tool servers
  • 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
  • Scenarios that need a service exposed AS an MCP server for Claude Desktop or other MCP clients to call — Kode does not provide that here
  • Security-sensitive environments requiring default-strict permission checks, since YOLO mode is on by default and --safe must be enabled manually
  • Simple, single-fixed-model use cases that don't need multi-model orchestration
  • 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 and write files in the working directory and subdirectories (editing/creating code)
  • Execute shell/Bash commands (no per-command confirmation by default in YOLO mode)
  • Make network requests: calls to configured model APIs, optional web tools, plugin/skill marketplace downloads, optional update checks
  • (Optional) run Bash commands inside a Linux bwrap sandbox with networking disabled by default, when --safe or KODE_SYSTEM_SANDBOX=1 is set
  • 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
  • Default YOLO mode skips permission prompts, so the model can modify files or run destructive commands without per-action approval
  • Externally connected MCP servers and marketplace-installed plugins/skills come from third parties and can introduce untrusted code execution paths
  • Multi-model orchestration means code and context are sent to whatever third-party model APIs the user configures, raising data-residency/privacy considerations
  • The README states the project is in a major refactoring/maintenance phase (July–December 2026), so interfaces, commands, or config formats may change
  • 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