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.

DimensionGEML MCP ServerAn MCP server for GEML documents, enabling block-at-a-time edits with validation.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS68 / 100 · C79 / 100 · B
Reliability12 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Documentation workflows that have adopted GEML.
  • Collaborative authoring with AI agents or scripts where safety is required.
  • Software development workflows that rely on documentation or code skeletons.
  • 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
  • Repositories that don't use GEML.
  • As a general-purpose file system tool.
  • Use cases requiring a network-accessible MCP server.
  • 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 and write access to files under the directory specified by --root, and only that directory.
  • Fetching packages on demand via npm/npx.
  • Ability to create and write .gemlhistory sidecar files inside the root.
  • 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
  • Misconfigured --root may cause unexpected changes, but writes outside the directory are explicitly refused.
  • Invalid document modifications are refused, but network access is needed for package installation.
  • History files may grow over time; tracking quotas is outside the root.
  • Vulnerable to misconfiguration of clients or tools; ensure the --root path is correct.
  • 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, Generic MCP clientClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools120