# adhikasp/mcp-git-ingest [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/adhikasp/mcp-git-ingest  
**GitHub Stars:** 312  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/adhikasp-mcp-git-ingest

## Description
Read and analyze GitHub repositories with your LLM

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "mcp-git-ingest": {
    "command": "uvx",
    "args": ["--from","git+https://github.com/adhikasp/mcp-git-ingest","mcp-git-ingest"]
  }
}
```

## Documentation

## What adhikasp/mcp-git-ingest MCP server does

The adhikasp/mcp-git-ingest MCP server gives an MCP client two focused ways to inspect a GitHub repository. One tool returns a tree-like view of the repository's directories and files. The other accepts a list of file paths and returns their contents in a path-to-content mapping.

This combination supports repository-oriented questions such as identifying the main source files, locating configuration, or reading selected implementation files after first examining the project layout. The server is intended for analysis rather than for editing, committing, or otherwise mutating repository contents.

## How it works

For each request, the server obtains a local copy of the repository using Git operations. A temporary directory name is derived deterministically from the repository URL, allowing the implementation to recognize an existing clone before cloning again. The directory-tree operation recursively walks the checked-out files, excludes the `.git` directory, sorts entries, and formats the result with Unicode tree characters.

The file-reading operation receives explicit paths from the MCP client and reads those files from the checked-out repository. Both operations handle failures such as clone or file-read errors and return descriptive error information. Cleanup is performed after processing through `finally` blocks, so temporary working data is removed when the operation completes.

The implementation uses FastMCP to expose the MCP interface and GitPython for repository operations. The project specifies Python 3.8 or newer.

## Setup and configuration

The adhikasp/mcp-git-ingest MCP server can be launched with `uvx` directly from its Git repository. An MCP client configuration uses `uvx` as the command, passes the repository URL with `--from`, and then invokes the `mcp-git-ingest` executable:

```json
{
  "mcpServers": {
    "mcp-git-ingest": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/adhikasp/mcp-git-ingest",
        "mcp-git-ingest"
      ]
    }
  }
}
```

The documented setup does not specify environment variables, API keys, or additional server configuration. The repository also describes a CLI entry point named `mcp-git-ingest`.

## Tools and capabilities

- `github_directory_structure`: clones the repository, builds a visual directory tree, and omits `.git` contents.
- `github_read_important_files`: clones the repository, reads the requested file paths, and returns their contents.
- Repository inspection: accepts a GitHub repository URL as the input for both operations.
- Error handling: reports clone and file-reading problems instead of requiring the client to handle uncaught failures.

## Limitations and notes

The adhikasp/mcp-git-ingest MCP server documents read and analysis operations only. It does not describe tools for changing files, creating commits, opening pull requests, or managing GitHub issues. File contents must be requested through explicit paths; the material does not describe automatic selection beyond the example workflow where a client first gets the directory structure and then chooses important files.

Temporary cloning and cleanup are part of each operation's behavior. Although deterministic directory naming can allow an existing clone to be reused, the documented processing flow also removes temporary repositories after use. No authentication method or private-repository support is specified, so access requirements for repositories needing credentials are not established by the provided material.

_Full upstream README: https://allmcps.com/mcp/adhikasp-mcp-git-ingest/readme_