Skip to main content
Glama
narayana-reddy-circles

MCP Git Status Server

Related Servers

Alternatives to MCP Git Status Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with git repositories by providing real-time access to repository status, branch information, commit history, and file changes. Allows users to query their git workspace through natural language commands.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides comprehensive Git functionality to MCP clients, enabling users to manage repositories through operations like commits, diffs, and branch management via natural language. It automatically detects the current working directory and supports multi-project workflows across different local environments.
      16
      100 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to analyze local Git repositories with commit logs, diffs, blame, statistics, and branch analysis using native git commands without requiring a GitHub API.
      24 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables Git repository interaction and automation via LLMs, providing tools to read, search, and manipulate Git repositories.
      15
      107 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: git-log retrieves commit history, while git-status provides current repository state. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tools follow a consistent 'git-' prefix with descriptive suffixes (log, status), using kebab-case throughout. The naming pattern is perfectly uniform.

    Tool Count2/5

    With only 2 tools, the server feels thin for a Git status domain. While the tools cover basic status and log operations, typical Git workflows would benefit from additional tools (e.g., diff, branch, stash).

    Completeness2/5

    For a Git status server, the surface is significantly incomplete. It lacks tools for common Git operations like diff, branch status, remote status, or staging area inspection, which limits agent effectiveness.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues