Skip to main content
Glama
jmiedzinski

MCP Git Explorer

by jmiedzinski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GIT_EXPLORER_GITLAB_TOKENNoYour GitLab personal access token for accessing private repositories

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_codebaseA
    Clone a Git repository and generate a structured text file containing its contents.

    This tool clones a git repository from the provided URL, processes its contents,
    and returns a single text file containing the repository structure and the content
    of all files. Binary files and empty text files are excluded. The tool respects
    .gitignore and .repomixignore patterns. The output includes an estimated token count
    using the o200k_base encoding.

    Args:
        repo_url (str): The URL of the Git repository to clone
        use_token (bool, optional): Whether to use the GitLab token for authentication.
                                   Defaults to True.

    Returns:
        str: A formatted text representation of the repository contents, including
             file structure, estimated token count, and the content of all text files.

    Raises:
        GitCommandError: If there is an error during the git clone operation
        Exception: For any other errors that occur during processing
estimate_codebaseA
    Get statistics about a Git repository without downloading all content.

    This tool clones a git repository from the provided URL, analyzes its structure,
    and returns statistical information useful for LLM processing, including:
    - Estimated token count
    - Total file count
    - Repository structure

    Args:
        repo_url (str): The URL of the Git repository to clone
        use_token (bool, optional): Whether to use the GitLab token for authentication.
                                   Defaults to True.

    Returns:
        str: A formatted text representation of the repository statistics

    Raises:
        GitCommandError: If there is an error during the git clone operation
        Exception: For any other errors that occur during processing
check_gitlab_token_statusA

Check if the GitLab token is configured in the environment. Returns: A message indicating whether the GitLab token is configured

get_fileA
    Fetch the content of a single specified file from a Git repository.

    This tool clones a Git repository from the provided URL, reads the content
    of the specified file, and returns it as a string. The repository is cloned
    with depth=1 for efficiency. If the file does not exist or an error occurs,
    an appropriate error message is returned.

    Args:
        repo_url (str): The URL of the Git repository to clone.
        file_path (str): The relative path to the file within the repository.
        use_token (bool, optional): Whether to use the GitLab token for authentication.
                                   Defaults to True.

    Returns:
        str: The content of the specified file, or an error message if retrieval fails.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation4/5

The tools are mostly distinct: get_codebase returns full content, estimate_codebase returns statistics, get_file retrieves a single file, and check_gitlab_token_status checks configuration. There is minor overlap between get_codebase and estimate_codebase (both analyze the repo), but their outputs are clearly different.

Naming Consistency5/5

All tool names follow the verb_noun pattern in snake_case (get_, check_, estimate_). The naming is consistent and predictable, with no mixed conventions.

Tool Count5/5

Four tools is well-suited for a Git explorer. The scope is focused on repository inspection, and each tool serves a distinct purpose without bloat or excessive overlap.

Completeness4/5

The tool set covers the core needs: full codebase extraction, single file retrieval, and statistics. A minor gap is the lack of a dedicated tool for listing the repository tree without content, though estimate_codebase partially addresses this. Overall, it is reasonably complete for its stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources