# TamiShaks-2/git-context-mcp [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/TamiShaks-2/git-context-mcp  
**GitHub Stars:** 3  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tamishaks-2-git-context-mcp

## Description
Local MCP server that provides structured Git repository analysis (project status, recent activity, code map, and risk hotspots) for AI coding agents.

## Tools
Capabilities this server exposes over MCP:

- **project_status** — Repository state awareness
- **code_map** — Structural understanding
- **recent_activity** — Development churn analysis
- **work_summary** — High-level progress overview
- **risk_scan** — Maintenance risk detection

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "git-context-mcp": {
    "command": "npx",
    "args": ["-y","tamishaks-2-git-context-mcp"]
  }
}
```

## Documentation

## What TamiShaks-2/git-context-mcp MCP server does

The TamiShaks-2/git-context-mcp MCP server gives AI coding agents a structured view of a local Git repository. It focuses on context extraction rather than repository manipulation. The output is intended to help an agent determine the project’s current state, understand its layout, see which areas have been changing, and identify files that may deserve additional care.

Analysis covers both Git information and repository files. The server operates locally and exposes read-only tools, so it does not change tracked files, upload the codebase, or run the project’s code. It also does not rely on external services or APIs.

## How it works

The server runs as a standalone local MCP process using STDIO transport. An MCP client connects to the process and invokes analysis tools against a local Git repository. The repository must be available on the machine where the server runs, and Git must be installed and available through the system PATH.

A practical analysis sequence starts with `project_status` to establish branch, cleanliness, and synchronization information. `code_map` can then provide a structural view of directories and important files. `recent_activity` shows development churn, while `work_summary` gives a broader progress and technical-debt view. `risk_scan` adds signals for files that may have elevated maintenance or bug risk.

## Setup and configuration

The project requires Python 3.10 or newer and a local Git installation. The documented setup creates a virtual environment, activates it, and installs the repository in editable mode with `pip install -e .`. The server is then launched with the Python executable from that environment and `src/server.py` as its argument.

For MCP Inspector, configure the transport as STDIO. The repository documentation shows the virtual-environment Python executable as the command and `src/server.py` as the argument. No API keys, hosted endpoint, or service account is described. Tests can be run with `pytest` from the project environment.

## Tools and capabilities

The TamiShaks-2/git-context-mcp MCP server exposes five read-only tools:

- `project_status`: Reports repository state, including branch, cleanliness, and synchronization details.
- `code_map`: Builds a structural directory view and identifies important files or entry points.
- `recent_activity`: Examines Git history to surface frequently modified or actively changing areas.
- `work_summary`: Produces a high-level view of recent work and open technical-debt indicators.
- `risk_scan`: Flags files associated with size, complexity, or high change frequency.

Together, these tools provide high-level machine-readable context rather than raw source-code dumps. The TamiShaks-2/git-context-mcp MCP server is therefore suited to an initial repository assessment before code changes or review.

## Limitations and notes

The server is local-first: it requires access to an existing Git repository and does not provide a hosted analysis service. Its documented scope is analysis, not editing, committing, synchronizing, or executing application code. The available material does not describe configurable environment variables, authentication, repository selection flags, or additional transports beyond STDIO.

Risk and activity results are analysis signals, not guarantees that a file contains a defect or should not be changed. Agents should use the results as context alongside the repository’s own code, tests, and review practices.

_Full upstream README: https://allmcps.com/mcp/tamishaks-2-git-context-mcp/readme_