Gitingest

Provides access to Git repository analysis via MCP, enabling summary, tree, and content retrieval with automatic ingestion.

typescript

0

GitHub Stars

typescript

Language

6 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mattdepaolis-mattdepaolis-gitingest-mcp": {
      "command": "uvx",
      "args": [
        "gitingest_mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "github_pat_...",
        "NODE_OPTIONS": "--max-old-space-size=4096"
      }
    }
  }
}

You can access Git repository analysis through a dedicated MCP server that uses the gitingest library to analyze repositories and present the data in a format tailored for large language models. This setup handles repository ingestion automatically, so you can start querying content right away.

How to use

Choose an MCP client and connect to your gitingest MCP server. Start by requesting a summary of a repository to verify ingestion and get a high-level overview. If you want deeper exploration, request the tree resource to see the repository structure, or the content resource to fetch file contents (subject to size limits). You can restrict what is ingested with include_patterns and exclude_patterns to keep responses focused and fast.

How to install

Prerequisites you need before starting: install Node.js and a suitable package manager, then prepare the MCP server configuration. You will run the MCP server via an MCP client workflow that uses the runtime command shown in the configuration.

Step-by-step setup you can follow now:

Ensure Node.js is installed on your system. You can verify with node -v and npm -v.
Prepare the MCP server configuration file that defines how to start the server. Use the stdio method shown below to run the MCP server locally.
Run the MCP server through the MCP runtime. The example uses the runtime command uvx with your server name as an argument.
Verify the server is running by connecting with an MCP client and requesting a repository summary.

Configuration and notes

The server defines an MCP entry that uses a runtime command to start. You can supply a GitHub Personal Access Token to access private repositories. Set the token in the environment so it remains persistent across restarts.

Security note: protect the token and limit its scope to repository read access. If you are working within a project that requires multiple tokens for different repositories, you can provide additional tokens in separate environment blocks or manage them via your environment manager.

Examples

Minimal ready-to-run configuration for a local MCP stdio server that uses uvx to start. This config enables automatic ingestion and makes the gitingest tool available through the MCP interface.

Troubleshooting

If you encounter connectivity or ingestion issues, verify that the server process is running and that the MCP client is pointing to the correct local or remote endpoint. Check that the required environment variable for private repository access is set and accessible by the server process. If ingestion seems slow for large repositories, apply include_patterns and exclude_patterns to narrow the scope.

Available tools

gitingest

Analyses Git repositories and exposes repository data through MCP resources. Supports requests for summary, tree, and content resources with size controls and include/exclude patterns.