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.

DimensionMCP Server TauriGive your AI assistant superpowers for Tauri developmentMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS54 / 100 · D79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers using Tauri v2
  • Those wanting AI assistance in building, testing, and debugging Tauri apps
  • Teams needing UI automation testing in Tauri applications
  • 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
  • Non-Tauri v2 projects
  • Scenarios requiring headless browser automation (like Selenium or Playwright)
  • General web automation unrelated to Tauri development
  • 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
  • Requires access to running Tauri app (via WebSocket port 9223)
  • May need system command execution permissions (e.g., launching simulators)
  • Requires write access to project files for plugin configuration
  • 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
  • Tools may contain bugs (project states developed with agentic coding tools)
  • Executing arbitrary IPC commands could cause unexpected behavior or data modification
  • Automation features may affect app state, use with caution
  • External dependencies (like Xcode, Android SDK) may need additional setup
  • 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, Cursor, Windsurf, VS Code, Cline, Roo Cline, Zed, Goose, Warp, CodexClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools200