Gitingest MCP Server
# Gitingest MCP Server
A Model Context Protocol (MCP) server implementation that integrates with [gitingest](https://github.com/cyclotruc/gitingest) for turning any Git repository into a simple text digest of its codebase.
<a href="https://glama.ai/mcp/servers/@narumiruna/gitingest-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@narumiruna/gitingest-mcp/badge" alt="Gitingest Server MCP server" />
</a>
## Features
- Easy integration with AI assistants through the Model Context Protocol
- Git repository analysis and ingestion capabilities
- Support for filtering files by size, patterns, and branches
- Returns comprehensive repository information including summaries, file structure, and content
## Usage
### Configuration Options
Add the following configuration to your AI assistant's settings to enable gitingest-mcp as an MCP server:
#### PyPI Installation
```json
{
"mcpServers": {
"gitingestmcp": {
"command": "uvx",
"args": ["gitingestmcp@latest"]
}
}
}
```
#### GitHub Installation
```json
{
"mcpServers": {
"gitingestmcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/narumiruna/gitingest-mcp",
"gitingestmcp"
]
}
}
}
```
#### Local Installation
```json
{
"mcpServers": {
"gitingestmcp": {
"command": "uv",
"args": [
"run",
"--directory",
"/home/<user>/workspace/gitingest-mcp",
"gitingestmcp"
]
}
}
}
```
## API
The server provides the following tool:
### `ingest_git`
Analyzes a Git repository and returns its content in a structured format.
#### Parameters:
- `source`: The URL of a Git repository or a local directory path
- `max_file_size` (optional): Maximum allowed file size in bytes (default: 10MB)
- `include_patterns` (optional): Pattern or set of patterns specifying files to include (e.g., "\*.md, src/")
- `exclude_patterns` (optional): Pattern or set of patterns specifying files to exclude
- `branch` (optional): The branch to clone and analyze (default: "main")
#### Returns:
A string containing:
1. Repository summary
2. Tree-like structure of the files
3. Content of the repository files
## Resources
- gitingest website: https://gitingest.com/
- gitingest repository: https://github.com/cyclotruc/gitingest
## License
See the [LICENSE](LICENSE) file for details.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'ingest_git' has a clearly defined purpose that is distinct by default.
A single tool inherently has perfect naming consistency. The tool name 'ingest_git' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.
One tool is too few for the apparent scope of a Git ingestion server. The tool description suggests capabilities like cloning, processing files, and returning summaries, structures, or content, which could reasonably be split into multiple specialized tools (e.g., clone_repo, list_files, get_file_content). A single tool feels thin and may force agents to handle complex parameter parsing.
The tool covers basic ingestion and file access, but there are notable gaps for a Git domain. Missing operations include version control actions (e.g., commit, branch, diff), repository management (e.g., create, delete), and more granular file operations. Agents can work around this by using the single tool for all tasks, but it lacks lifecycle coverage.