Skip to main content
Glama

Related Servers

Alternatives to Git MCP Server

No user-submitted related servers found.

    Related Servers

    • 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,381 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightweight MCP server that enables AI assistants to manage local Git repositories by executing commands like status, add, and commit. It streamlines development workflows by providing repository context and diffs directly to the assistant.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform standard Git operations like staging, committing, and pushing changes. It facilitates a high-quality, standardized workflow for managing code repositories through natural language commands.
      99 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants deep understanding of your local Git repositories, providing instant repo overviews, change summaries, blame analysis, changelogs, branch health checks, and history search.
      76 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 21 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Git operations with no ambiguity. For example, branch_create, branch_delete, and branch_list are clearly differentiated, and tools like stash_save, stash_pop, and stash_list cover distinct aspects of stash management without overlap.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as branch_create, tag_delete, remote_add, and stash_list. All tools use snake_case with clear, descriptive names that align with Git terminology, making the set predictable and readable.

    Tool Count3/5

    With 21 tools, the count is borderline high for a Git server, as it includes many specific operations that might be overwhelming. While comprehensive, a typical Git scope could be covered with fewer tools (e.g., 10-15), making this feel slightly heavy but still within reason for the domain.

    Completeness5/5

    The tool set provides complete coverage of core Git workflows, including repository management (init, clone), branching (create, delete, list), committing (add, commit), remote operations (add, list, remove, push, pull), and stash/tag handling. No obvious gaps exist, and agents can perform full CRUD/lifecycle operations seamlessly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues