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.

DimensionRepowiseCodebase intelligence layer: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions for AI agents and humans.MartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS66 / 100 · C79 / 100 · B
Reliability9 / 2012 / 20
Security and permissions13 / 2018 / 20
Maintenance15 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 20
Best for
  • Developers who want deep codebase insights locally without uploading code to the cloud.
  • Teams needing pre-merge change-risk scoring and code health metrics.
  • Those looking to provide structured context to AI coding agents to save tokens and improve accuracy.
  • 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 wanting a fully managed cloud service without any local installation (use hosted repowise.dev).
  • Slow index times may be a concern for large repos (e.g., 366s for Django), so not ideal if you need instant setup.
  • Non-technical users unfamiliar with command-line tools and MCP configuration.
  • 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 access to the specified repository's file system (mandatory).
  • Optional: send code snippets to LLM providers for prose generation (if AI-generated docs enabled).
  • Optional: write access to Git or GitHub for PR bot comments if installed.
  • Read access to Git history for analysis.
  • 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
  • Privacy: while local-first, enabling LLM prose or using hosted versions sends code to third parties.
  • Performance: indexing large repositories can take minutes, slowing initial setup.
  • Reliance on Python environment and pip; potential dependency conflicts.
  • Accuracy: heuristic-based scores and generated docs may be imperfect, especially for less-supported languages.
  • 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, Cursor, VS CodeClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools100