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.

DimensionOpen CoworkOpen-source personal AI agent desktop app with one-click install, multi-model support, sandbox isolation, and MCP integration.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS58 / 100 · C79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions12 / 2018 / 20
Maintenance14 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience11 / 2015 / 20
Best for
  • Users needing AI-powered desktop automation on Windows or macOS.
  • Users who want a GUI to use AI coding tools like Claude Code.
  • Security-conscious users who need sandbox isolation.
  • Users who need to generate professional document formats (PPTX, DOCX).
  • Teams that want to integrate remote control via Feishu or Slack.
  • 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
  • Linux users, as no official installer is provided (though you can build from source).
  • Advanced users who prefer command-line tools without a GUI.
  • Users with no API keys or who are sensitive to API costs.
  • Users needing fully offline operation, as AI functionality requires external API calls.
  • Users wanting to use non-standard models or custom endpoints, though OpenAI-compatible APIs are supported, extra configuration may be needed.
  • 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 access to the selected workspace folder.
  • Ability to execute commands in VMs (WSL2 or Lima).
  • Access to external services via MCP connectors (e.g., browser, Notion).
  • Network access to call AI model APIs and external services.
  • 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
  • AI operations may accidentally delete or modify files; use sandbox isolation and authorize carefully.
  • If sandbox is disabled, commands execute locally on the host, posing security risks.
  • API keys are stored locally; protect them from exposure.
  • Remote control features (like Feishu) can be abused; ensure access controls.
  • Third-party MCP connectors may introduce security risks; only use trusted ones.
  • 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
Tools50