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.

DimensionKilo CodeThe open source, all-in-one agentic engineering platformMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS30 / 100 · D79 / 100 · B
Reliability2 / 2012 / 20
Security and permissions6 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation8 / 2018 / 20
Setup experience4 / 2015 / 20
Best for
  • Developers who want one agent with access to 500+ switchable AI models across editor and terminal
  • Teams setting up automated pull request code reviews
  • Teams wanting an autonomous coding agent in CI/CD pipelines to fix failing tests or complete defined tasks
  • Users who prefer open source tooling billed at provider rates with no subscription markup
  • 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 standard MCP server that exposes specific tools/resources to connect to (the source material does not show Kilo Code offering this)
  • Fully offline scenarios with no external model provider account or network access
  • Environments where automatic terminal command execution and browser control cannot be trusted or permitted
  • 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
  • Terminal command execution, used to run and automate tasks
  • Browser control, used to automate web actions
  • Read/write access to local repository files for code generation and edits
  • With `--auto`, the agent can perform any action without confirmation prompts
  • 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
  • `--auto` disables all permission prompts, letting the agent execute any action unconfirmed — the README explicitly warns to only use it in trusted environments
  • Granting terminal and browser control carries risk of unintended or incorrect actions being executed
  • The agent's "self-checking" reviews its own work but does not guarantee correctness, so human review is still warranted
  • The source material does not describe data handling/privacy practices for the third-party model providers it connects to; check official docs before relying on it for sensitive code
  • 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