# Pare Git MCP server

> Lets AI clients run git status, log, diff, branch, and show commands and receive typed, schema-validated JSON instead of raw terminal text.

- Repository: https://github.com/Dave-London/Pare
- Page: https://hostedmcp.org/servers/dave-london/git
- Transport: stdio
- Stars: 141
- License: MIT
- Latest version: 0.8.0

## Install

### Claude Code

```sh
claude mcp add git -- npx -y @paretools/git
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/git"
      ]
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "git": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@paretools/git"
      ]
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"git","type":"stdio","command":"npx","args":["-y","@paretools/git"]}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/git"
      ]
    }
  }
}
```

### Codex

```sh
codex mcp add git -- npx -y @paretools/git
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.git]
command = "npx"
args = ["-y", "@paretools/git"]
```

### Gemini CLI

```sh
gemini mcp add -s user git npx -- -y @paretools/git
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "git": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/git"
      ]
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `PARE_GIT_TOOLS` | no | no |  |
| `PARE_NPM_TOOLS` | no | no |  |
| `PARE_TOOLS` | no | no |  |

## Tools (15)

- `status`: Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts). Use instead of running `git status` in the terminal.
- `log`: Returns commit history as structured data. Use instead of running `git log` in the terminal.
- `diff`: Returns file-level diff statistics as structured data. Use full=true for patch content. Use instead of running `git diff` in the terminal.
- `branch`: Lists, creates, or deletes branches. Returns structured branch data. Use instead of running `git branch` in the terminal.
- `show`: Shows commit details and diff statistics for a given ref. Use instead of running `git show` in the terminal.
- `add`: Stages files for commit. Returns structured data with count and list of staged files. Use instead of running `git add` in the terminal.
- `commit`: Creates a commit with the given message. Returns structured data with hash, message, and change statistics. Use instead of running `git commit` in the terminal.
- `push`: Pushes commits to a remote repository. Returns structured data with success status, remote, branch, and summary. Use instead of running `git push` in the terminal.
- `pull`: Pulls changes from a remote repository. Returns structured data with success status, summary, change statistics, and any conflicts. Use instead of running `git pull` in the terminal.
- `checkout`: Switches branches or restores files. Returns structured data with ref, previous ref, and whether a new branch was created. Use instead of running `git checkout` in the terminal.
- `tag`: Lists tags sorted by creation date. Returns structured tag data with name, date, and message. Use instead of running `git tag` in the terminal.
- `stash-list`: Lists all stash entries with index, message, and date. Returns structured stash data. Use instead of running `git stash list` in the terminal.
- `stash`: Pushes, pops, applies, or drops stash entries. Returns structured result with action, success, and message. Use instead of running `git stash` in the terminal.
- `remote`: Lists remote repositories with fetch and push URLs. Returns structured remote data. Use instead of running `git remote -v` in the terminal.
- `blame`: Shows commit annotations for a file, grouped by commit. Returns structured blame data with deduplicated commit metadata (hash, author, date) and their attributed lines. Use instead of running `git blame` in the terminal.

## FAQ

### What does the git MCP server return?

It returns structured, typed JSON for git operations such as status, log, diff, branch, and show, plus human-readable content for display.

### How do I limit which git tools are registered?

Set the PARE_GIT_TOOLS environment variable to a comma-separated list of tool names, for example status,log,diff.

### Does the git server use structured output schemas?

Yes, it uses MCP's structuredContent and outputSchema features so agents get validated, type-safe data.

### How does the git server reduce token usage?

It converts verbose raw git output into compact JSON, cutting tokens significantly; the README cites roughly 92% fewer tokens for a verbose git log.
