Skip to main content
Glama
Gitingest-MCP

Gitingest-MCP

by puravparab

吉廷格斯特-MCP铁匠徽章

用于gitingest的 MCP 服务器。这使得 Claude Desktop、Cline、Cursor 等 MCP 客户端能够快速提取 Github 仓库的信息,包括:

  • 存储库摘要

  • 项目目录结构

  • 文件内容

https://github.com/user-attachments/assets/c1fa596b-a70b-4d37-91d9-ea5e80284793

目录

Related MCP server: MCP GitHub Reader

安装

通过 Smithery 安装

  • 通过Smithery安装 gitingest-mcp :

    npx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client claude --config "{}" # Claude
    npx -y @smithery/cli@latest run @puravparab/gitingest-mcp --client cursor --config "{}" # Cursor
    npx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client windsurf --config "{}" # Windsurf
    npx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client cline --config "{}" # Cline

通过 Github 安装

  1. 将其添加到 MCP 客户端配置文件

    {
     "mcpServers": {
         "gitingest-mcp": {
             "command": "<path to uv>/uvx",
             "args": [
                 "--from",
                 "git+https://github.com/puravparab/gitingest-mcp",
                 "gitingest-mcp"
             ]
         }
     }
    }

手动安装 Repo

  1. 克隆 repo

    git clone https://https://github.com/puravparab/Gitingest-MCP
    cd Gitingest-MCP
  2. 安装依赖项

    uv sync
  3. 将其添加到 MCP 客户端配置文件

    {
     "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"
             ]
         }
     }
    }
  4. 如果您遇到问题,请按照此MCP 服务器文档进行操作

更新 MCP 客户端配置

  1. 添加到 Claude 桌面

    在 IDE 中打开配置文件

    cursor ~/Library/Application\ Support/Claude/claude_desktop_config.json
    code ~/Library/Application\ Support/Claude/claude_desktop_config.json

调试

  1. 使用 mcp 检查器

    uv run mcp dev src/gitingest_mcp/server.py

Available Tools

3 tools
git_filesC
Get 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)

Inputs: file_paths (required), owner (required), repo (required), branch.

git_summaryC
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)

Inputs: owner (required), repo (required), branch.

git_treeC
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)

Inputs: owner (required), repo (required), branch.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that wraps gitingest to enable Claude Code to analyze GitHub repositories, providing access to code structures, statistics, and full content. It facilitates the creation of structured study notes and supports both public and private repositories through the Model Context Protocol.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      A minimal MCP server for GitHub that enables browsing repos, reading code, searching, and getting insights through natural language via Claude, Cursor, or any MCP client.
      7
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that exposes GitHub user profiles, repository info, and search via tools for AI assistants like Claude.
      -