The Gitingest-MCP server allows MCP clients to extract information from GitHub repositories. You can:
Get repository summaries (including repo name, files, token count, and README summary)
Access project directory structure (tree structure of the repository)
Retrieve content of specific files within repositories
Allows MCP clients to extract information about Github repositories including repository summaries, project directory structure, and file content
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Gitingest-MCP show me the directory structure of the react repository"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server for gitingest. This allows MCP clients like Claude Desktop, Cline, Cursor, etc to quickly extract information about Github repositories including
Repository summaries
Project directory structure
File content
https://github.com/user-attachments/assets/c1fa596b-a70b-4d37-91d9-ea5e80284793
Related MCP server: MCP GitHub Reader
To install gitingest-mcp via Smithery:
npx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client claude --config "{}" # Claudenpx -y @smithery/cli@latest run @puravparab/gitingest-mcp --client cursor --config "{}" # Cursornpx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client windsurf --config "{}" # Windsurfnpx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client cline --config "{}" # ClineAdd this to the MCP client config file
{
"mcpServers": {
"gitingest-mcp": {
"command": "<path to uv>/uvx",
"args": [
"--from",
"git+https://github.com/puravparab/gitingest-mcp",
"gitingest-mcp"
]
}
}
}Clone the repo
git clone https://https://github.com/puravparab/Gitingest-MCP
cd Gitingest-MCPInstall dependencies
uv syncAdd this to the MCP client config file
{
"mcpServers": {
"gitingest": {
"command": "<path to uv>/uv",
"args": [
"run",
"--with",
"mcp[cli]",
"--with-editable",
"<path to gitingest-mcp project>/gitingest_mcp",
"mcp",
"run",
"<path to gitingest-mcp project>/gitingest-mcp/src/gitingest_mcp/server.py"
]
}
}
}If you have issues, follow this MCP server documentation
Add to Claude Desktop
Open config file in your IDE
cursor ~/Library/Application\ Support/Claude/claude_desktop_config.jsoncode ~/Library/Application\ Support/Claude/claude_desktop_config.jsonUsing mcp inspector
uv run mcp dev src/gitingest_mcp/server.pyGet the content of specific files from a GitHub repository
Args:
owner: The GitHub organization or username
repo: The repository name
file_paths: List of paths to files within the repository
branch: Optional branch name (default: None)
| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | ||
| file_paths | Yes | ||
| owner | Yes | ||
| repo | Yes |
Get a summary of a GitHub repository that includes
- Repo name,
- Files in repo
- Number of tokens in repo
- Summary from the README.md
Args:
owner: The GitHub organization or username
repo: The repository name
branch: Optional branch name (default: None)
| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | ||
| owner | Yes | ||
| repo | Yes |
Get the tree structure of a GitHub repository
Args:
owner: The GitHub organization or username
repo: The repository name
branch: Optional branch name (default: None)
| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | ||
| owner | Yes | ||
| repo | Yes |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0git_filesgit_summarygit_treeScored across 3 tools
Each tool has a clearly distinct purpose: git_files retrieves specific file contents, git_summary provides a high-level repository overview with metrics, and git_tree returns the repository's file/directory structure. There is no overlap in functionality - an agent can easily distinguish between getting file contents, getting structural information, or getting a summary.
All three tools follow a perfect 'git_' prefix pattern with descriptive suffixes (files, summary, tree). The naming is completely consistent in style, format, and verb usage, making the tool set immediately understandable and predictable.
With only 3 tools, this feels somewhat thin for a GitHub ingestion server. While the tools cover basic repository inspection (files, structure, summary), there are likely additional ingestion operations that would be useful, such as commit history retrieval, branch listing, or contributor information. The count is borderline minimal for the apparent scope.
The tool set covers fundamental repository inspection operations but has notable gaps for a comprehensive ingestion system. Missing are tools for retrieving commit history, branch information, contributor data, or issue tracking. While the existing tools provide a foundation, agents will encounter dead ends when needing more complete repository metadata beyond file content and structure.
An MCP server that gives your AI access to the source code and docs of all public github repos
Repository knowledge graph MCP server for codebase understanding and debugging.
A MCP server built for developers enabling Git based project management with project and personal…
