Skip to main content
Glama
martinsky999

MCP Git Server

by martinsky999

Related Servers

Alternatives to MCP Git Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server that enables LLMs to interact with Git repositories, providing tools to read, search, and manipulate Git repositories through commands like status, diff, commit, and branch operations.
      22
      4
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.
      12
      39,753 PyPI
      90,629
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides Git version control operations as structured tools for AI coding agents. It enables LLMs to programmatically manage repositories through actions like committing changes, rolling back code, and comparing diffs.
      10
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables Large Language Models to interact with Git repositories through a robust API, supporting operations like repository initialization, cloning, file staging, committing, and branch management.
      28
      3,590 npm
      241
      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.
      148 npm
      -
    • A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that provides 29 Git operations and advanced workflows, enabling AI assistants and developers to safely manage version control.
      30
      379 npm
      1
      ISC

    TDQS

    B3.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. The tools map directly to specific Git commands (add, checkout, commit, diff, etc.) with clear boundaries between operations like git_diff, git_diff_staged, and git_diff_unstaged that target different states of changes.

    Naming Consistency5/5

    All tools follow a perfect and consistent verb_noun pattern with the 'git_' prefix (e.g., git_add, git_checkout, git_commit). There are no deviations in naming conventions, making the set highly predictable and readable.

    Tool Count5/5

    With 12 tools, this is well-scoped for a Git server covering core version control operations. Each tool earns its place by addressing essential Git workflows (e.g., staging, committing, branching, diffing, logging), without being overly sparse or bloated.

    Completeness5/5

    The tool surface provides complete coverage of the Git domain for basic to intermediate operations. It includes initialization (git_init), staging (git_add), committing (git_commit), branching (git_create_branch, git_checkout), diffing (git_diff variants), history (git_log, git_show), and status management (git_status, git_reset), with no obvious gaps for core workflows.