Skip to main content
Glama
modelcontextprotocol

git MCP server

Official

Related Servers

Alternatives to git MCP 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
      D
      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 management.
      12
      MIT
    • A
      license
      A
      quality
      B
      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,619 npm
      242
      Apache 2.0
    • 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
      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.
      176 npm
      ISC

    TDQS

    B3/5.0

    Scored across 12 tools

    Disambiguation4/5

    The three diff tools (git_diff_unstaged, git_diff_staged, git_diff) are distinguished by scope, but an agent must read descriptions carefully to choose correctly. Other tools target unique actions/resources, with only minor overlap between git_show and git_log.

    Naming Consistency5/5

    All tools consistently use a git_ prefix and snake_case, matching familiar Git subcommands. No mixed conventions or ambiguous naming styles are present.

    Tool Count5/5

    12 tools is well-scoped for a Git server covering core local operations. Each tool earns its place without excessive bloat or thin coverage.

    Completeness3/5

    The set covers staging, committing, diffing, branching, checkout, log, and show, but omits notable Git lifecycle operations such as branch deletion, merge, rebase, remote push/pull, and stash. Core local workflows work, but the surface is not complete for general Git use.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week