git-tools
Related Servers
Alternatives to git-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform full Git operations including branching, committing, pushing, stashing, rebasing, and more, with safety features and support for advanced workflows like Git Flow and LFS.117 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run structured preflight checks and identity-scoped Git operations, committing, pushing and opening GitHub PRs with the correct Git name, email, SSH key and signature for each repository. Persistent changes require exact proposals, human approval by default and recoverable, idempotent apply.155 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceEnables autonomous coding agents to inspect Git commits, create pull requests, parse issue threads, and post reviews on GitHub repositories.-
- AlicenseBqualityDmaintenanceEnables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.10145 npmISC
- AlicenseAqualityBmaintenanceEnables AI agents to safely read, search, and inspect a local git repository, including PR-style diffs and changed-file summaries. It also supports opt-in allowlisted test runs.4MIT
TDQS
Scored across 10 tools
The tools separate cleanly by resource and action: rebase start/resume/read/split and commit read/stage/create/amend/verify are distinct. The only mild overlap is git_commit_read's "amend" advice versus git_commit_amend performing the rewrite, but the read-only framing keeps them separable.
All names follow a consistent git_<resource>_<action> snake_case pattern. The resource groups (rebase, commit, repo) and action suffixes are predictable throughout.
Ten tools are well scoped for a specialized stacked-branch git workflow. Each tool covers a distinct operation, and none feels redundant or gratuitous.
The surface covers repository/stack reading, commit inspection, staging hunks, creating/amending/verifying commits, and starting/resuming/splitting rebases. The main gap is the lack of an explicit fetch tool despite repo_read advising a fetch, and publishing/pushing is deliberately left outside the tool set.