F
licenseNot graded
qualityD
maintenanceExposes GitHub actions as tools for creating branches, pushing files, opening and merging pull requests.
-
Git Workflow Automation MCP Server
by Arcia125
Related Servers
Alternatives to Git Workflow Automation MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI assistants to perform Git workflows with semantic commit messages, pre-PR secret audits, conflict resolution, and release changelog generation.5MIT
- FlicenseAqualityCmaintenanceEnables inspecting local Git repositories and automating delivery tasks such as status checks, diffs, commits, pull requests, and deployments using git and GitHub CLI.6-
- FlicenseNot gradedqualityDmaintenanceEnables high-level GitHub workflows such as cloning, branching, committing, pushing, creating pull requests and issues, all verified step-by-step via git and gh CLI.-
- AlicenseAqualityDmaintenanceEnables AI assistants to create conventional Git commits, update changelogs, and optionally push changes to remote repositories.22MIT
- 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.-
TDQS
C2.8/5.0
Scored across 4 tools
Disambiguation2/5
Multiple tools have overlapping purposes that could cause confusion. The 'complete_git_workflow' tool appears to encompass functionality of both 'git_commit_and_push' and 'create_pull_request', making it unclear when to use which tool. While 'merge_pull_request' is distinct, the boundaries between the other three tools are poorly defined.
Naming Consistency3/5
The naming conventions are mixed with no clear pattern. 'complete_git_workflow' uses a descriptive phrase format, 'create_pull_request' and 'merge_pull_request' follow a verb_noun pattern, and 'git_commit_and_push' uses a compound verb format. While all names are readable, the inconsistency in structure creates a disjointed feel.
Tool Count2/5
With only 4 tools, this server feels significantly under-scoped for Git workflow automation. A proper Git workflow server would typically need tools for staging changes, checking status, branching, reviewing PRs, and handling conflicts. The current set is too thin to support comprehensive workflow automation.
Completeness2/5
There are significant gaps in the Git workflow coverage. Missing are essential operations like staging changes, creating/checking out branches, viewing repository status, reviewing/commenting on PRs, and handling merge conflicts. The server provides only endpoint operations without the supporting tools needed for a complete workflow.
Maintenance
ActivityInactive
ResponsivenessNo issues