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.

DimensionChat UIOpen-source chat interface with OpenAI-compatible API and MCP tool support.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS52 / 100 · D79 / 100 · B
Reliability3 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers needing to build or customize an AI chat interface.
  • Teams looking to leverage MCP tools to enhance model capabilities.
  • Developers familiar with the Hugging Face ecosystem seeking quick deployment.
  • 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 requiring non-OpenAI-compatible API integrations (removed in this version).
  • Users who need a simple chat interface without MCP functionality.
  • 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 environment variables to configure API keys.
  • Network access to connect to OpenAI-compatible endpoints and MCP servers.
  • File system access to store database persistence data (if using embedded MongoDB).
  • 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
  • API key leakage risk: keys in environment variables may be exposed, especially in deployment.
  • MCP server security risk: adding untrusted MCP servers could lead to tool misuse or data leakage.
  • Dependency risk: reliance on external APIs and MCP servers, whose availability and behavior 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 DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools10