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.

DimensionXcodebuild MCP ServerMCP tool for building Xcode iOS projects and feeding back errors to LLMsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS41 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance8 / 2016 / 20
Documentation10 / 2018 / 20
Setup experience8 / 2015 / 20
Best for
  • iOS developers using Visual Studio Code with AI extensions (e.g., Cline, Roo Code)
  • AI coding workflows that require quick build and test of iOS projects
  • 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 needing a GUI-based build tool
  • Users not working with Xcode or iOS development
  • Those requiring advanced build configurations (e.g., signing, certificate management)
  • 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
  • Reads the full path of the specified folder
  • Executes xcodebuild commands to build or test the project
  • 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
  • Builds may take a long time; ensure appropriate timeout settings
  • Builds may consume significant CPU and memory
  • Incorrect project paths may cause build failures
  • 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, Cline, Roo CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools20