Git Summary vs Gitlab MCP
A side-by-side look at the Git Summary and Gitlab MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git Summary for version control work as a local process; choose Gitlab MCP for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git Summary when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
git_summary, git_changes, git_blame.
Choose Gitlab MCP when
- You need dedicated capabilities in the Version Control domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_API_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 55/100 · Good | 36/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITLAB_PERSONAL_ACCESS_TOKENGITLAB_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,061 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Git Summary | View Gitlab MCP |
Tools & capabilities
Git Summary tools 6
git_summaryGet a structured overview of a Git repository: current branch, recent commits, contributors, and repo stats. Works on any local Git repo.git_changesGet a summary of changes in a commit range: what files changed, who changed them, and a diff stat. Useful for understanding what happened between two points in history.git_blameAnalyze who wrote each line of a file, when, and in which commit. Get top contributors and ownership breakdown. Optionally limit to a line range.git_changelogAuto-generate a changelog from Git commits. Groups commits by type (feat, fix, docs, etc.) using conventional commit format. Specify a range or get the full log.git_branch_healthAnalyze all local branches: find stale branches, merged branches ready for cleanup, and branches that are ahead/behind. Helps keep your repo tidy.git_searchSearch through Git history for commits matching a query. Searches both commit messages and code changes (pickaxe search). Find when a change was introduced or a bug was created.
Gitlab 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.
Git Summary
{
"mcpServers": {
"git-summary": {
"command": "npx",
"args": [
"-y",
"git-summary-mcp"
]
}
}
}
Gitlab MCP
No confirmed install command for Gitlab MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Git Summary is categorized under Version Control and uses a local stdio subprocess. Gitlab MCP belongs to Version Control and uses an install path we have not confirmed yet. Pick Git Summary for version control work and Gitlab 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. Gitlab MCP has no confirmed install command yet — follow its own setup instructions.
Git Summary has no declared pricing — check the project's own site. Gitlab MCP has no declared pricing — check the project's own site. Auth: api key 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 git-summary and gitlab-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git Summary has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Gitlab MCP has 36/100 (Fair) with 0 views, 0 installs and 2,061 GitHub stars.