Skip to main content
Glama
Git Workflow Automation MCP Server

Git Workflow Automation MCP Server

by Arcia125

Git Workflow Automation MCP Server

A Model Context Protocol (MCP) server that provides automated Git workflow tools for committing, creating pull requests, and merging with proper GitHub authentication handling.

Features

  • Automated Git Operations: Commit, push, create PRs, and merge in one command

  • GitHub Authentication Handling: Automatically clears problematic environment tokens

  • Dry Run Support: Test operations before executing them

  • Conventional Commits: Supports proper commit message formatting

  • Branch Management: Automatic branch creation and switching

  • Error Handling: Comprehensive error reporting and rollback capabilities

Related MCP server: GitHub MCP Server

Available Tools

1. git_commit_and_push

Commits staged changes and pushes to remote repository.

Parameters:

  • files (array, optional): File paths to commit (empty for all changes)

  • commitMessage (string, required): Commit message (use conventional format)

  • branch (string, optional): Branch name to create/switch to

  • workingDir (string, optional): Working directory path

  • dryRun (boolean, optional): Preview without executing

Example:

use_mcp_tool("git-workflow", "git_commit_and_push", {
  "files": ["src/app.ts", "README.md"],
  "commitMessage": "feat: add new authentication system",
  "branch": "feature/auth-system",
  "dryRun": true
})

2. create_pull_request

Creates a GitHub pull request with proper authentication handling.

Parameters:

  • title (string, required): Pull request title

  • body (string, required): Pull request description

  • baseBranch (string, optional): Base branch (default: "main")

  • headBranch (string, optional): Head branch (defaults to current)

  • workingDir (string, optional): Working directory path

  • dryRun (boolean, optional): Preview without executing

Example:

use_mcp_tool("git-workflow", "create_pull_request", {
  "title": "Feature: User Authentication System",
  "body": "Implements comprehensive user authentication with JWT tokens and OAuth2 support",
  "baseBranch": "main",
  "headBranch": "feature/auth-system"
})

3. merge_pull_request

Merges a GitHub pull request.

Parameters:

  • prNumber (string, required): Pull request number

  • mergeMethod (string, optional): "merge", "squash", or "rebase" (default: "merge")

  • deleteBranch (boolean, optional): Delete branch after merge (default: true)

  • workingDir (string, optional): Working directory path

  • dryRun (boolean, optional): Preview without executing

Example:

use_mcp_tool("git-workflow", "merge_pull_request", {
  "prNumber": "42",
  "mergeMethod": "squash",
  "deleteBranch": true
})

4. complete_git_workflow

Executes the complete Git workflow: commit, push, create PR, and optionally merge.

Parameters:

  • files (array, optional): Files to commit

  • commitMessage (string, required): Commit message (conventional format)

  • prTitle (string, required): Pull request title

  • prBody (string, required): Pull request description

  • branch (string, optional): Feature branch name

  • baseBranch (string, optional): Base branch (default: "main")

  • autoMerge (boolean, optional): Automatically merge PR (default: false)

  • workingDir (string, optional): Working directory path

  • dryRun (boolean, optional): Preview without executing

Example:

use_mcp_tool("git-workflow", "complete_git_workflow", {
  "files": ["src/**/*.ts", "docs/**/*.md"],
  "commitMessage": "feat(auth): implement OAuth2 authentication",
  "prTitle": "Feature: OAuth2 Authentication System",
  "prBody": "Adds comprehensive OAuth2 authentication with Google and GitHub providers",
  "branch": "feature/oauth2-auth",
  "autoMerge": false,
  "dryRun": true
})

Installation

Quick Setup

  1. Clone the Repository

    git clone https://github.com/Arcia125/git-workflow-mcp-server.git
    cd git-workflow-mcp-server
  2. Install Dependencies

    npm install
  3. Build the Server

    npm run build
  4. Add to MCP Configuration

    Add the server to your MCP client settings file:

    {
      "mcpServers": {
        "git-workflow": {
          "command": "node",
          "args": ["/path/to/git-workflow-mcp-server/build/index.js"],
          "disabled": false,
          "alwaysAllow": [],
          "disabledTools": []
        }
      }
    }

Alternative: NPM Global Install (Coming Soon)

Future versions will support global npm installation:

npm install -g git-workflow-mcp-server

Configuration Paths

Common MCP Settings Locations:

  • Roo-Code: %APPDATA%/Code - Insiders/User/globalStorage/rooveterinaryinc.roo-cline/settings/mcp_settings.json

  • Claude Desktop: %APPDATA%/Claude/claude_desktop_config.json

  • Other MCP Clients: Check your client's documentation for settings location

Verify Installation

Test the installation with a dry run:

use_mcp_tool("git-workflow", "git_commit_and_push", {
  "files": ["README.md"],
  "commitMessage": "test: verify MCP server installation",
  "dryRun": true
})

Prerequisites

  • Node.js installed

  • Git configured with remote repository

  • GitHub CLI (gh) installed and authenticated

  • Proper GitHub repository permissions

Authentication

The server automatically handles GitHub authentication issues by:

  1. Clearing problematic environment tokens (GITHUB_TOKEN, GH_TOKEN)

  2. Using PowerShell commands for reliable token management

  3. Relying on GitHub CLI keyring authentication

  4. Providing detailed error messages for authentication failures

Best Practices

1. Always Use Dry Run First

// Test the operation first
use_mcp_tool("git-workflow", "complete_git_workflow", {
  "commitMessage": "feat: add new feature",
  "prTitle": "New Feature",
  "prBody": "Description",
  "dryRun": true
})

// Then execute after confirmation
use_mcp_tool("git-workflow", "complete_git_workflow", {
  "commitMessage": "feat: add new feature",
  "prTitle": "New Feature",
  "prBody": "Description",
  "dryRun": false
})

2. Use Conventional Commits

// Good commit messages:
"feat(auth): add OAuth2 integration"
"fix(ui): resolve button alignment issue"
"docs(api): update endpoint documentation"
"refactor(utils): simplify date formatting"

3. Meaningful PR Titles and Descriptions

{
  "prTitle": "Feature: OAuth2 Authentication System",
  "prBody": "## Changes\n- Implements OAuth2 with Google/GitHub\n- Adds JWT token management\n- Updates user authentication flow\n\n## Testing\n- All auth tests pass\n- Manual testing completed"
}

Error Handling

The server provides comprehensive error handling:

  • Git Repository Errors: Validates repository state

  • Authentication Failures: Handles GitHub CLI auth issues

  • Network Issues: Provides clear error messages

  • Branch Conflicts: Manages branch creation/switching

  • Merge Conflicts: Reports merge issues clearly

Dependencies

  • @modelcontextprotocol/sdk: MCP server framework

  • simple-git: Git operations

  • axios: HTTP requests (if needed)

  • zod: Schema validation

Development

To modify the server:

  1. Edit src/index.ts

  2. Run npm run build

  3. Restart your MCP client

Support

For issues or questions:

  • Check GitHub CLI authentication: gh auth status

  • Verify repository permissions

  • Review error messages for specific guidance

  • Test with dry run mode first

Version

Version 0.1.0 - Initial release with core Git workflow automation features.

Available Tools

4 tools
complete_git_workflowA

Execute complete Git workflow: commit, push, create PR, and optionally merge

Inputs: commitMessage (required), prTitle (required), prBody (required), files, +5 more.

create_pull_requestC

Create a GitHub pull request with proper authentication handling

Inputs: title (required), body (required), baseBranch, headBranch, +2 more.

git_commit_and_pushC

Commit staged changes and push to remote repository

Inputs: commitMessage (required), files, branch, workingDir, +1 more.

merge_pull_requestC

Merge a GitHub pull request

Inputs: prNumber (required), mergeMethod, deleteBranch, workingDir, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers