GitHub Repository Intelligence vs Git MCP
A side-by-side look at the GitHub Repository Intelligence and Git MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GitHub Repository Intelligence for version control work over a hosted endpoint; choose Git MCP for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Git MCP 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | APIFY_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 8,472 |
| Directory activity | 2 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View GitHub Repository Intelligence | View Git MCP |
Tools & capabilities
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?"
Git MCP tools
No tool names declared yet. Check the project README from the listing page.
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.
GitHub Repository Intelligence
{
"mcpServers": {
"github-repository-intelligence": {
"url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp"
}
}
}
Git MCP
{
"mcpServers": {
"idosal-git-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
Frequently asked questions
GitHub Repository Intelligence is categorized under Version Control and uses a remote HTTP/SSE transport. Git MCP belongs to Version Control and uses a local stdio subprocess. Pick GitHub Repository Intelligence for version control work and Git MCP 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.
GitHub Repository Intelligence has no declared pricing — check the project's own site. Git MCP is listed as free. Auth: no auth required. 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 github-repository-intelligence and idosal-git-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitHub Repository Intelligence has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Git MCP has 49/100 (Fair) with 7 views, 0 installs and 8,472 GitHub stars.