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를 설치하려면:

    지엑스피1

    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. 저장소를 복제합니다

    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 Desktop에 추가

    IDE에서 구성 파일을 엽니다.

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

디버그

  1. mcp inspector 사용하기

    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.
      -