Skip to main content
Glama
mcp-git-ingest

mcp-git-ingest

by adhikasp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
git_directory_structureB

Clone a Git repository and return its directory structure in a tree format.

git_read_important_filesC

Read the contents of specified files in a given git repository.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one exposes repository structure, the other reads file contents. There is no realistic overlap in selection, since listing a tree and reading files are separate operations.

Naming Consistency3/5

Both tools use snake_case and a shared git_ prefix, but the naming pattern is mixed: git_directory_structure is resource-oriented while git_read_important_files is verb-oriented. They remain readable, but the convention is not fully predictable.

Tool Count3/5

Two tools is thin for a repository-ingestion server, even though each tool has a distinct role. The surface is just barely sufficient for basic use, but it sits at the low end of appropriate scope.

Completeness3/5

The server covers basic cloning, structure discovery, and file reading, but it lacks branch/ref selection, commit metadata, search, and broader file-discovery operations. These are notable gaps for a git-ingestion workflow, though simple use cases can still proceed.

Maintenance

ActivityNo data
ResponsivenessOutdated data