Git vs GitHub Repository Intelligence
A side-by-side look at the Git and GitHub Repository Intelligence MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for version control work as a local process; choose GitHub Repository Intelligence for version control over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Choose GitHub Repository Intelligence when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
APIFY_TOKEN. - You want tools like
get_repo_overview, list_recent_prs, get_contributors.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | APIFY_TOKEN |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,526 | 0 |
| Directory activity | 51 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 6 |
| Full listing | View Git | View GitHub Repository Intelligence |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
GitHub Repository Intelligence tools 6
get_repo_overview"Is this repo still maintained?"list_recent_prs"Show me the last 20 merged PRs by user X"get_contributors"Who maintains this project?"get_hot_files"Where's the churn?"get_ci_status"Is the default branch green?"get_dependencies"What does this project depend on?"
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
GitHub Repository Intelligence
{
"mcpServers": {
"github-repository-intelligence": {
"url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp"
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. GitHub Repository Intelligence belongs to Version Control and uses a remote HTTP/SSE transport. Pick Git for version control work and GitHub Repository Intelligence for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Git is listed as free. Auth: no auth required. GitHub Repository Intelligence has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add git and github-repository-intelligence as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 51 views, 0 installs and 91,526 GitHub stars. GitHub Repository Intelligence has 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.