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.

DimensionSemSemantic version control on top of Git, giving AI coding agents entity-level code intelligenceMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS69 / 100 · C79 / 100 · B
Reliability11 / 2012 / 20
Security and permissions14 / 2018 / 20
Maintenance13 / 2016 / 20
Documentation17 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Developers using AI coding agents who want to reduce token consumption
  • Teams that need cross-file impact analysis and entity-level diffs
  • Projects working in Git repos that want deterministic dependency-graph answers instead of grep results
  • 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 who do not use an MCP client
  • Scenarios needing browser automation, cloud storage, or database access
  • Users wanting a zero-install experience: running sem mcp requires the sem binary to be installed first
  • 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 local code repository files
  • Store a SQLite entity cache and query index on the local machine (by default under the OS cache directory; overridable with SEM_CACHE_DIR)
  • Optional: log in to sem cloud via the GitHub device flow with sem login (only needed for cloud acceleration)
  • 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
  • The sem binary name conflicts with the sem binary shipped by GNU Parallel; run sem --version to check which one you are using
  • The entity cache is stored outside the repository by default under the OS cache directory, and setting SEM_CACHE_DIR can change its location
  • Cloud queries are opt-in per repo; logging in does not by itself upload a repo or send a query, but enabling cloud queries does send data to sem cloud
  • Local telemetry records command names on your own machine only and uploads nothing in that mode; opting in uploads counts, and SEM_NO_TELEMETRY=1 or DO_NOT_TRACK=1 forces the record-nothing behavior
  • Agents issue read queries against repository code, so ensure their working directory and permission scope match your expectations
  • 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, Cursor, Claude DesktopClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools80