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.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS66 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance15 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 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.
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
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.
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
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.
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
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.
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Codex, Cursor, VS CodeClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1015