Skip to main content
Glama
saitolume

git-mcp-server

by saitolume

Related Servers

Alternatives to git-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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.
      99 npm
      1
      GPL 3.0
    • F
      license
      A
      quality
      D
      maintenance
      MCP server for managing Git operations on local repositories, allowing users to list repositories, get and create tags, list commits, push tags, and refresh repositories through a standardized interface.
      6
      3
      -
    • 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
      A lightweight MCP server that handles git operations on behalf of AI coding assistants, running as a local HTTP service without external network exposure by default.
      MIT

    TDQS

    A4.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct Git operation (branch creation, staging, fetch, commit, merge, push, result retrieval) with no overlap. The merge-related tools (merge, continue, abort) are clearly differentiated by their stage in the merge lifecycle.

    Naming Consistency5/5

    All tool names follow a consistent 'git_' prefix + snake_case verb_noun pattern (e.g., git_switch_create, git_restore_worktree, git_merge_continue). The naming is predictable and easy to parse.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a focused Git workflow (branch, stage, commit, fetch, merge, push). It avoids bloat while covering essential operations, and each tool serves a clear purpose.

    Completeness4/5

    The tool surface covers core development operations (add, commit, push, fetch, merge, branch creation) but lacks common operations like log, diff, or stash. While the set is coherent for a linear workflow, minor gaps reduce coverage.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues