A
licenseA
qualityB
maintenanceA local MCP server that provides a safe, explicit set of Git operations for version control tasks like status, diff, branching, staging, committing, fetching, merging, and pushing.
13
13 npm
MIT
Git Stuff Server
by skurekjakub
Related Servers
Alternatives to Git Stuff Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA specialized MCP server for in-depth analysis of git repositories, offering tools for branch overview, time period analysis, file changes, and merge recommendations.47Apache 2.0
- AlicenseAqualityBmaintenanceMCP server for git archaeology — churn hotspots, blame summaries, bus factor, commit forensics and file history over any local repository.113MIT
- AlicenseBqualityDmaintenanceMCP Server for Git operations, agent templates, and project utilities.952 npmMIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server exposing Git branch diff sessions, filtered file lists, patches, and commit metadata from the Branch Diff Explorer VS Code extension to local AI clients.MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server providing SQLite querying, port checking, and git diff summary tools for local development.MIT
TDQS
C2.9/5.0
Scored across 4 tools
Disambiguation4/5
Three tools (ado_pr_changes, ado_pr_comment, ado_pr_threads) are clearly distinct and focused on Azure DevOps pull request operations, with no overlap in their purposes. The fourth tool (git_merge_diff) is unrelated to Azure DevOps and operates on local Git repositories, creating a minor domain mismatch but no functional ambiguity.
Naming Consistency2/5
The naming is inconsistent across the tool set. The first three tools use a consistent 'ado_pr_' prefix with descriptive suffixes (changes, comment, threads), but the fourth tool uses a different 'git_' prefix with a different structure (merge_diff). This mixed convention reduces predictability and coherence.
Tool Count3/5
With only 4 tools, the count feels thin for a server named 'Git Stuff Server', which implies broader Git-related functionality. The tools are split between Azure DevOps PR operations and a local Git diff tool, making the scope appear fragmented rather than comprehensive.
Completeness2/5
For Azure DevOps pull requests, the tools cover fetching changes, commenting, and fetching threads, but lack core operations like creating, updating, or merging pull requests. For local Git operations, only one diff tool is provided, missing basic commands like clone, commit, or push. This results in significant gaps that will hinder agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues