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.

DimensionGit MCP ServerA comprehensive Git MCP server for AI agents.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS61 / 100 · C76 / 100 · B
Reliability10 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Development teams needing broad native Git CLI capabilities through MCP.
  • Local or server deployments requiring STDIO or Streamable HTTP.
  • Deployments needing working-directory restrictions, authentication, structured logging, or optional telemetry.
  • 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
  • Pure edge environments that do not provide the local Git CLI; the isomorphic-git provider is listed as planned.
  • Cloud-native GitHub API operations without a local repository; the GitHub API provider is listed only as a possible roadmap item.
  • Workflows that expect destructive cleaning or hard resets without confirmation.
  • 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
  • It needs access to and permission to modify local Git repositories and file paths within the configured scope.
  • A local Git installation is required because the current provider uses the Git CLI.
  • GPG or SSH signing setup is needed if commit signing is enabled; signing is enabled by default.
  • HTTP deployments using JWT or OAuth require the corresponding authentication secret or OIDC issuer URL.
  • 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
  • Commit, push, merge, rebase, cherry-pick, tag, and worktree operations can change repository state or remote content.
  • git clean and git reset --hard are destructive and require explicit confirmation.
  • Without GIT_BASE_DIR, operations may cover a broader accessible directory tree.
  • HTTP authentication defaults to none; authentication and access controls should be configured before public deployment.
  • If signing fails, the server silently falls back to unsigned output and reports signed and signingWarning fields.
  • 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 clientsClineClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools2815