← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionDesktop Touch MCPWindows computer-use MCP server: drive any desktop app with semantic discover-then-act targeting.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS45 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions9 / 2018 / 20
Maintenance7 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience9 / 2015 / 20
Best for
  • Windows users wanting AI agents to operate desktop apps intuitively.
  • Developers using Claude or Cursor for end-to-end desktop testing.
  • Those needing high-fidelity UI automation with low token overhead.
  • 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
  • macOS or Linux – Windows only.
  • Those needing pixel-coordinate-based automation exclusively (though available).
  • Games or RDP sessions where UIA fails and must rely on OCR.
  • Headless environments – requires an interactive desktop.
  • 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 screen content (screenshots).
  • Enumerate UI elements via Windows UI Automation API.
  • Simulate keyboard and mouse input.
  • Control browsers via CDP.
  • Access filesystem for screenshot and log caching.
  • Store credentials encrypted with DPAPI.
  • 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
  • Malicious prompts could cause destructive actions: deleting files, downloading malware. Since the agent can control the desktop, use in a sandboxed environment if possible.
  • Credentials are stored locally encrypted with DPAPI, but Key Locker uses unsigned helper executable (SmartScreen may warn).
  • Automation could inadvertently interfere with other apps; user supervision is advised.
  • Could be used for keylogging or unauthorized data access if not properly configured.
  • 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 Desktop, Claude Code, Cursor, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools320