Gitingest-MCP

@opengig

About Gitingest-MCP

No overview available yet

#gitingest #mcp-server #github-integration

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "gitingest-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "install",
        "@puravparab/gitingest-mcp",
        "--client",
        "claude",
        "--config",
        "{}",
        "#",
        "Claude"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Gitingest-MCP?

Gitingest-MCP is an MCP server for the gitingest tool. It allows MCP clients like Claude Desktop, Cline, Cursor, and Windsurf to quickly extract repository summaries, project directory structure, and file content from GitHub repositories.

How to use Gitingest-MCP?

Install via Smithery (npx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client <client>), via GitHub using uvx, or manually by cloning the repo and running uv sync. Then add the appropriate configuration to your MCP client config file (e.g., claude_desktop_config.json).

Key features of Gitingest-MCP

Extracts GitHub repository summaries, directory structure, and file content.
Supports multiple MCP clients (Claude Desktop, Cline, Cursor, Windsurf).
Installable via Smithery, GitHub, or manual repository clone.
Uses uv for dependency and runtime management.

Use cases of Gitingest-MCP

Quickly understanding the structure and contents of a GitHub repository.
Feeding repository context to an AI assistant for code analysis or documentation.
Automating repository information retrieval in various MCP‑compatible editors.

FAQ from Gitingest-MCP

What information can Gitingest-MCP retrieve from a repository?

It can retrieve repository summaries, the project directory structure, and file content.

What are the runtime dependencies?

The server requires uv and git (for manual installation). It runs as a Python‑based MCP server.

Where does the data come from?

All data is fetched live from GitHub repositories via the gitingest integration.

Are there any known limits or authentication requirements?

No authentication or rate limits are mentioned in the README. The server interacts with public GitHub repositories by default.

How is the server transported and configured?

The server uses stdio transport. Configuration is done by adding a JSON entry to the MCP client’s configuration file (e.g., claude_desktop_config.json).

Frequently asked questions