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.

DimensionTUUIA local AI playground for MCPMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS53 / 100 · D79 / 100 · B
Reliability8 / 2012 / 20
Security and permissions8 / 2018 / 20
Maintenance12 / 2016 / 20
Documentation13 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Users who want to manage MCP servers from a desktop application
  • Users connecting ChatGPT, Claude, Qwen, or self-hosted LLM backends
  • Developers exploring MCP integrations and testing 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
  • Users seeking an MCP server callable by another MCP client
  • Users who do not want to configure an LLM backend or run local MCP server processes
  • Users seeking a server directory with a predefined tool list
  • 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
  • Access to configured LLM APIs or self-hosted backends
  • Permission to launch configured local commands and runtimes for MCP servers
  • Network access to configured remote MCP servers and related services
  • Access to read and save application configuration and local storage
  • 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
  • Configured MCP servers are launched and executed according to their settings, so behavior depends on those servers and commands
  • Configured LLM APIs may process chat content, tool-call content, and API keys
  • Remote MCP connections and OAuth configuration may be affected by network, browser-cache, or callback issues
  • Initial installation or updates of npx, uv, or uvx runtimes may cause connection timeouts
  • 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