AgentBay
Sign InGet Started
MCP Serverv1.0.0

Git Workflow MCP Server

MCP server with 10 tools for AI agents to manage git branches, commits, PRs, code review, and release workflows via GitHub API.

by AgentBay Official
Unrated
0 purchases0 reviews VerifiedVerified 3/5/2026
Free

Code is provided "as is". Review and test before production use. Terms

gitgithubmcppull-requestcode-reviewci-cdrelease
A

Built by AgentBay Official

@agentbay-official

16 listings
Unrated
Summary

MCP server with 10 git/GitHub tools: create_branch (from any ref), commit_changes (stage and commit with message), open_pull_request (with title, body, reviewers), list_pull_requests (with filters), review_pull_request (approve/request-changes/comment), merge_pull_request (merge/squash/rebase), create_release (with changelog generation), get_ci_status (check GitHub Actions), list_branches (with staleness info), resolve_conflicts (interactive merge assistance). Uses GitHub API with personal access token.

Use Cases
  • Automate feature branch creation and PR workflows
  • Have your AI agent open PRs for code changes it makes
  • Automate release creation with generated changelogs
  • Check CI/CD status before merging PRs
  • Clean up stale branches automatically
Integration Steps

Step 1: Create a GitHub personal access token with repo scope at github.com/settings/tokens

Step 2: Add the MCP server to your agent config

File: mcp.json

{
  "mcpServers": {
    "git": {
      "command": "node",
      "args": ["./node_modules/@agentbay/git-mcp/dist/index.js"],
      "env": {
        "GITHUB_TOKEN": "${GITHUB_TOKEN}",
        "GITHUB_OWNER": "your-username",
        "GITHUB_REPO": "your-repo"
      }
    }
  }
}

Step 3: Your agent can now use git tools like create_branch and open_pull_request

Anti-Patterns
  • Do not force-push to main/master branches
  • Do not merge PRs without checking CI status first
  • Do not create releases from non-default branches without explicit confirmation
Limitations
  • GitHub only — no GitLab, Bitbucket, or Azure DevOps support
  • Requires a GitHub personal access token with repo scope
  • Large diffs (>500 files) may be truncated in review tools
  • Cannot resolve complex merge conflicts automatically
Environment Variables
GITHUB_TOKENRequiredSensitiveGitHub personal access token with repo scope
GITHUB_OWNERRequiredGitHub repository owner
GITHUB_REPORequiredGitHub repository name
AI Verification Report
Passed
Overall73%
Security70%
Code Quality75%
Documentation65%
Dependencies95%
3 files analyzed217 lines read17.6sVerified 3/5/2026

Findings (15)

  • -Documentation claims 10 tools but only 10 are implemented; however, documentation lists different tool names (e.g., 'create_branch', 'commit_changes', 'open_pull_request') while code implements 'github_create_branch', 'github_commit_file', 'github_create_pr'. Tool naming is inconsistent.
  • -Documentation claims 'commit_changes (stage and commit with message)' but code only has 'github_commit_file' which creates/updates individual files, not a full staging workflow.
  • -Documentation claims 'review_pull_request (approve/request-changes/comment)' tool but this is not implemented in code.
  • -Documentation claims 'resolve_conflicts (interactive merge assistance)' tool but this is not implemented in code.
  • -Documentation claims 'get_ci_status (check GitHub Actions)' tool but this is not implemented in code.
  • +10 more findings

Suggestions (9)

  • -Update documentation to match actual tool names (github_*) or rename code to match docs. Currently 6/10 documented tools are missing or named differently.
  • -Implement missing tools: review_pull_request, get_ci_status, resolve_conflicts. These are documented but not implemented.
  • -Add validation for GITHUB_TOKEN at startup. Check for presence and warn if DEFAULT_OWNER or DEFAULT_REPO are missing.
  • +6 more suggestions
Loading version history...
Loading reviews...