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.

DimensionApple Docs MCP ServerAccess Apple Developer Documentation, WWDC videos, and Swift/Objective-C code examples seamlessly in AI assistants.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS59 / 100 · C79 / 100 · B
Reliability7 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance10 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Apple developers
  • iOS/macOS developers
  • Developers using AI coding assistants like Claude and Cursor
  • 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
  • Developers not working on Apple platforms
  • Users needing real-time WWDC data (the package includes 2014-2025 data)
  • Users needing a local offline mirror of all documentation (though WWDC data is offline accessible)
  • 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 network access to fetch Apple Developer Documentation (except WWDC data, which is bundled locally)
  • Does not require file system access, but communicates with clients via MCP protocol
  • 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
  • Relies on public Apple Developer APIs, which may be rate-limited or unavailable
  • Caching may delay documentation updates (up to 2 hours)
  • Non-official project, no guarantee of compatibility with future Apple API changes
  • 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 Code, Windsurf, Zed, Cline, Amazon Q Developer CLIClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools150