Gitingest MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub Personal Access Token (PAT) for accessing private repositories. The gitingest library will automatically use this environment variable. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitingestB | Access Git repository data with automatic ingestion as needed |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'gitingest' has a clearly defined purpose of accessing Git repository data with automatic ingestion, making it impossible for an agent to confuse it with other tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'gitingest' follows a single pattern with no deviations or mixing of conventions to evaluate, ensuring predictability.
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or overly narrow scope. For a Git-related server, one tool is insufficient to cover typical operations like cloning, committing, or branching, making it feel thin and underdeveloped.
The tool surface is severely incomplete for a Git domain. While 'gitingest' handles data access and ingestion, it lacks essential operations such as repository management, version control actions, or querying specific Git objects, leading to significant gaps that will likely cause agent failures in broader workflows.