🚀 Auggie Git MCP Server

A Git integration server for the Auggie CLI using the Model Context Protocol (MCP). This server provides Git operations as tools that can be used by AI assistants through Auggie.

✨ Features

🎯 Flexible Tool Modes

Choose the right set of tools for your workflow:

Core Mode - Essential Git workflow

• git_status - Check repository status
• git_add - Add files to staging area
• git_commit - Commit changes
• git_push - Push to remote

Standard Mode - Recommended for most users (Default)

• All core tools plus:
• git_pull - Pull from remote
• git_log - View commit history
• git_diff - Show file differences
• git_branch - Manage branches

Full Mode - For power users

• All standard tools plus advanced features:
• git_stash - Manage stash operations
• git_reset - Reset repository state
• git_merge - Merge branches
• git_tag - Manage tags
• Analysis tools (git_blame, git_show, etc.)

🔧 Enhanced Features

• Smart Error Handling - Context-aware error messages with recovery suggestions
• Configurable Tool Sets - Choose exactly which tools you need
• Environment Configuration - Override settings with environment variables
• Structured Logging - Debug and monitor server operations
• TypeScript - Full TypeScript support with type definitions

📦 Installation

Method 1: Global Installation with pnpm

pnpm add -g auggie-git
pnpm exec auggie-git install-auggie

Method 2: Using npx (No Installation Required)

Configure Auggie to use npx:

auggie mcp add git \
  --command npx \
  --args "-y auggie-git@latest"

🔧 Configuration

Quick Start - Core Tools Only

Create ~/.auggie-git.json:

{
  "server": {
    "toolsMode": "core"
  }
}

Standard Configuration (Default)

{
  "server": {
    "toolsMode": "standard",
    "logLevel": "info"
  },
  "git": {
    "defaultRemote": "origin",
    "defaultBranch": "main"
  }
}

Power User Configuration

{
  "server": {
    "toolsMode": "full",
    "enableConsoleOutput": true
  },
  "git": {
    "confirmDestructive": true,
    "maxLogEntries": 20
  }
}

Environment Variables

export AUGGIE_GIT_LOG_LEVEL=debug
export AUGGIE_GIT_DEFAULT_REMOTE=upstream
export AUGGIE_GIT_DEFAULT_BRANCH=develop

For detailed configuration options, see CONFIGURATION.md.

Method 3: Local Development

git clone <repository-url>
cd auggie-git
pnpm install
pnpm build
pnpm link --global
pnpm exec auggie-git install-auggie

🔧 Configuration

After installation, the server will be automatically configured in your Auggie settings. The configuration will look like this:

{
  "mcpServers": {
    "auggie-git": {
      "command": "auggie-git",
      "args": []
    }
  }
}

🛠️ Available Tools

Core Operations

• git_status - Repository status with porcelain/human-readable options
• git_commit - Stage and commit changes with custom messages
• git_push - Push to remote with configurable options
• git_pull - Pull changes with rebase/merge options
• git_log - Commit history with formatting options
• git_diff - File differences with various comparison modes

Branch & State Management

• git_branch - Create, switch, delete, rename branches
• git_stash - Save, apply, pop, list stashed changes
• git_merge - Merge branches with different strategies
• git_reset - Reset repository state (soft/mixed/hard)
• git_tag - Create, list, delete, show tags

Analysis & Information

• git_blame - Line-by-line authorship information
• git_show - Detailed commit and object information
• git_remote - Manage remote repositories
• git_repo_info - Comprehensive repository analysis

For detailed parameter information, see API Documentation.

📚 Usage Examples

Basic Workflow

1. Check repository status:

   Use the git_status tool to see what files have changed

2. Commit changes:

   Use git_commit with message "Add new feature implementation"

3. Push to remote:

   Use git_push to push changes to origin

Advanced Usage

• View recent commits: git_log with limit: 5 and oneline: true
• See staged changes: git_diff with staged: true
• Force push: git_push with force: true (use carefully!)

⚙️ Configuration

Create a .auggie-git.json file in your home directory or project root:

{
  "server": {
    "logLevel": "info",
    "enableConsoleOutput": true,
    "timeout": 30000
  },
  "git": {
    "defaultRemote": "origin",
    "defaultBranch": "main",
    "autoStage": true,
    "confirmDestructive": true,
    "maxLogEntries": 10,
    "pushStrategy": "simple"
  },
  "aliases": {
    "st": "status",
    "co": "checkout",
    "br": "branch"
  }
}

Environment Variables

• AUGGIE_GIT_LOG_LEVEL - Set logging level (debug, info, warn, error)
• AUGGIE_GIT_DEFAULT_REMOTE - Override default remote
• AUGGIE_GIT_WORKING_DIR - Set working directory

🔄 Development

Quick Setup

pnpm install
pnpm dev-setup    # Sets up development environment
pnpm build
pnpm test:mcp     # Test MCP protocol compliance

Available Scripts

pnpm build        # Compile TypeScript
pnpm dev          # Run in development mode
pnpm test         # Run unit tests
pnpm test:mcp     # Test MCP protocol
pnpm lint         # Run ESLint
pnpm validate     # Validate implementation

📋 Requirements

• Node.js >= 18
• Git installed and configured
• Auggie CLI installed

🤝 Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request

📄 License

MIT License - see LICENSE file for details.

🆘 Troubleshooting

Server Not Starting

• Ensure Node.js >= 18 is installed
• Check that Git is available in your PATH
• Verify Auggie configuration is correct

Git Commands Failing

• Make sure you're in a Git repository
• Check Git configuration (user.name, user.email)
• Verify you have appropriate permissions for the repository

Installation Issues

• Try clearing pnpm cache: pnpm store prune
• Ensure you have write permissions to global pnpm directory
• Check that Auggie is properly installed and configured

🔗 Links

• Model Context Protocol
• Auggie CLI
• TypeScript MCP SDK