Skip to main content
Glama
Gitingest MCP Server

Gitingest MCP Server

by narumiruna

Gitingest MCP 服务器

模型上下文协议 (MCP) 服务器实现与gitingest集成,将任何 Git 存储库转换为其代码库的简单文本摘要。

特征

  • 通过模型上下文协议轻松与人工智能助手集成

  • Git 存储库分析和提取功能

  • 支持按大小、模式和分支过滤文件

  • 返回全面的存储库信息,包括摘要、文件结构和内容

Related MCP server: GitHub MCP Server

用法

配置选项

将以下配置添加到您的 AI 助手的设置中,以启用 gitingest-mcp 作为 MCP 服务器:

PyPI 安装

{
  "mcpServers": {
    "gitingestmcp": {
      "command": "uvx",
      "args": ["-U", "gitingestmcp"]
    }
  }
}

GitHub 安装

{
  "mcpServers": {
    "gitingestmcp": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/narumiruna/gitingest-mcp",
        "gitingestmcp"
      ]
    }
  }
}

本地安装

{
  "mcpServers": {
    "gitingestmcp": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/home/<user>/workspace/gitingest-mcp",
        "gitingestmcp"
      ]
    }
  }
}

API

服务器提供以下工具:

ingest_git

分析 Git 存储库并以结构化格式返回其内容。

参数:

  • source :Git 存储库的 URL 或本地目录路径

  • max_file_size (可选):允许的最大文件大小(以字节为单位)(默认值:10MB)

  • include_patterns (可选):指定要包含的文件的模式或模式集(例如“*.md,src/”)

  • exclude_patterns (可选):指定要排除的文件的模式或模式集

  • branch (可选):要克隆和分析的分支(默认值:“main”)

返回:

包含以下内容的字符串:

  1. 存储库摘要

  2. 文件的树状结构

  3. 存储库文件的内容

资源

执照

有关详细信息,请参阅LICENSE文件。

Available Tools

1 tool
ingest_gitC

This function analyzes a source (URL or local path), clones the corresponding repository (if applicable), and processes its files according to the specified query parameters. It can return a summary, a tree-like structure of the files, or the content of the files.

Inputs: source (required), branch, exclude_patterns, include_patterns, +1 more.

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 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'ingest_git' has a clearly defined purpose that is distinct by default.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency. The tool name 'ingest_git' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.

    Tool Count2/5

    One tool is too few for the apparent scope of a Git ingestion server. The tool description suggests capabilities like cloning, processing files, and returning summaries, structures, or content, which could reasonably be split into multiple specialized tools (e.g., clone_repo, list_files, get_file_content). A single tool feels thin and may force agents to handle complex parameter parsing.

    Completeness3/5

    The tool covers basic ingestion and file access, but there are notable gaps for a Git domain. Missing operations include version control actions (e.g., commit, branch, diff), repository management (e.g., create, delete), and more granular file operations. Agents can work around this by using the single tool for all tasks, but it lacks lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers