Gitingest
About
Analyze Git repositories and provide content optimized for large language models.
Details
- Author
- trelisresearch
- Categories
- Developer Tools, Other, Knowledge Base
Jump to
Setup
Install Gitingest in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/trelisresearch/trelis-gitingest-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
An MCP server for gitingest that provides access to Git repository analysis through the Model Context Protocol (MCP). This server leverages the gitingest library to analyze Git repositories and make their content available in a format optimized for LLMs.
[!WARNING] Private repo support in gitingest is not yet on PyPI as of June 25th 2025. Once that is pushed, this MCP will automatically support it.
This MCP server provides a single unified tool for accessing Git repository data. It automatically handles repository ingestion as needed, so users can immediately query repository content without an explicit ingestion step.
The server provides a single tool calledgitingestthat can be used to analyze Git repositories. The tool accepts the following parameters:
- repo_uri(required): URL or local path to the Git repository
- resource_type: Type of data to retrieve (summary,tree,content, orall). Default issummary.
- max_file_size: Maximum file size in bytes to include in the analysis. Default is 10MB.
- include_patterns: Comma-separated patterns of files to include in the analysis.
- exclude_patterns: Comma-separated patterns of files to exclude from the analysis.
- branch: Specific branch to analyze.
- output: File path to save the output to.
- max_tokens: Truncates the response to a specified number of tokens.
You can ingest private GitHub repositories by providing a GitHub Personal Access Token (PAT).
Recommended:Set an Environment Variable in your MCP Config
This is the best approach for persistent configuration. Add anenvblock to your server definition in your MCP configuration file. Thegitingestlibrary will automatically use theGITHUB_TOKENenvironment variable.
"mcpServers": { "trelis-gitingest-mcp": { "command": "uvx", "args": [ "trelis-gitingest-mcp" ], "env": { "GITHUB_TOKEN": "github_pat_..." } } }
For large repositories, it's recommended to first request only thesummary(which is the default). After ingestion, you can access more detailed information through the resources:
- Use thetreeresource to explore the repository structure
- Use thecontentresource to access the full content (if not too large)
If the repository is too large, consider usinginclude_patternsand/orexclude_patternsto limit the scope of the ingestion.
After you call thegitingesttool for a repository, the server defines resources for that repository:
- Summary: A high-level summary of the repository
- Tree: The file/directory structure
- Content: The full content (subject to size limits)
These resources can be accessed individually via the resources interface in any MCP-compatible client. This is useful for browsing or fetching specific aspects of a repository after ingestion.
To use this MCP server from PyPI, add the following to your MCP config:
"mcpServers": { "trelis-gitingest-mcp": { "command": "uvx", "args": [ "trelis-gitingest-mcp" ] } }
To run directly from the GitHub repository:
"mcpServers": { "trelis-gitingest-mcp": { "command": "uvx", "args": [ "git+https://github.com/TrelisResearch/trelis-gitingest-mcp" ] } }
To prepare the package for distribution:
- Sync dependencies and update lockfile:
uv sync
The best way to debug MCP servers is with theMCP Inspector.
You can launch the Inspector with your local server using this command:
npx @modelcontextprotocol/inspector uv --directory /Users/RonanMcGovern/TR/trelis-gitingest-mcp run trelis-gitingest-mcp
npx @modelcontextprotocol/inspector uvx https://github.com/TrelisResearch/trelis-gitingest-mcp.git
npx @modelcontextprotocol/inspector uvx trelis-gitingest-mcp
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
Local stdio MCP server that lets AI coding agents read and maintain structured architecture, rules, and decisions directly from your repository.
Anchor is local repo and org memory for AI coding agents. It indexes GitHub PR history, current code, tests, regressions, architecture, and cross-repo impact locally, then exposes concise cited context through MCP and CLI workflows. Local-first. Read-only GitHub access. No CLI telemetry. No SaaS. No remote LLM calls.
An intelligent system for managing programming rules, supporting search, versioning, code validation, and prompt enhancement.
Git-native decision memory for coding agents, stored as git trailers and refs/notes.
Make git commits on behalf of AI to track AI contributions in your codebase.
Generates Conventional Commits style commit messages using LLM providers like DeepSeek and Groq.
Interact with the GitHub API for file operations, repository management, and search.
AI drafts the commits, you decide what ships. GitInProgress lets your AI read your uncommitted working tree and propose how to split it into focused commit candidates — each with a draft commit message. Nothing lands in git history until you review and approve; the AI never commits on its own.
Transforms any GitHub project into a documentation hub, enabling AI tools to access up-to-date documentation and code.
An MCP server for interacting with and automating Git repositories using Large Language Models.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
