Skip to main content
Glama

Related Servers

Alternatives to Git MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A local MCP server that provides a safe, explicit set of Git operations for version control tasks like status, diff, branching, staging, committing, fetching, merging, and pushing.
      13
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A secure, git-aware MCP server for working with local repositories, enabling file management, shell commands, and full git operations within allowed directories.
      148 npm
      1
      GPL 3.0
    • A
      license
      C
      quality
      B
      maintenance
      An MCP server that enables AI agents to inspect and interact with a local Git repository, including managing Git status, logs, branches, commits, and workspace files.
      8
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Git repositories, enabling AI assistants to manage repositories, branches, commits, and files through a standardized interface.
      3,590 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables managing Git repositories via shallow clones and analyzing them with CodeGraph. It provides tools for adding, listing, updating, deleting repositories, and exploring codegraph status and exploration.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides Git version control operations for Claude, enabling comprehensive repository management. It allows users to perform tasks such as staging files, committing changes, managing branches, and handling remote operations like pushing and pulling.
      136 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: creating tags, getting the last tag, listing commits since the last tag, listing repositories, pushing tags, and refreshing repositories. The descriptions reinforce these distinct functions, making misselection unlikely.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create_git_tag, list_commits_since_last_tag) with clear, descriptive names. The only minor deviation is 'refresh_repository' which uses 'refresh' instead of a more common verb like 'update', but it still fits the pattern and is understandable.

    Tool Count5/5

    With 6 tools, this server is well-scoped for managing git repositories, focusing on tag operations and repository maintenance. Each tool serves a specific, useful function without bloat, making the count appropriate for the domain.

    Completeness3/5

    The toolset covers tag management and basic repository operations well, but there are notable gaps in the git domain, such as creating commits, branching, merging, or handling remotes beyond pushing tags. This limits agents from performing full git workflows, though the provided tools are coherent for their specific scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues