Skip to main content
Glama
abhinav054

git-remote-mcp

by abhinav054
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to git-remote-mcp

No user-submitted related servers found.

    Related Servers

    • git-mcp-server

      saitolume
      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
      18
      MIT

    • Cross Repo Ops MCP

      DHCross
      F
      license
      B
      quality
      C
      maintenance
      Enables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.
      10
      -

    • mcp-git

      William12556
      A
      license
      Not graded
      quality
      A
      maintenance
      A local git MCP server. It exposes 12 git operations to an MCP client over stdio, allowing the client to inspect and work with a git repository on your machine, including status, diffs, log, branches, staging, and commits.
      MIT

    • Git MCP Server

      yevheniikravchuk
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables git repository operations through REST endpoints, providing access to repository status, diffs, and commits. Enforces security through configurable root directory allowlists for safe git operations.
      -

    • void-bridge

      intricos777-dot
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes a secure, path-confined bridge to a local workspace and git remotes, enabling MCP clients to search, read, write, reset files, and perform git operations.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    C2.5/5.0

    Scored across 27 tools

    Disambiguation2/5

    The generic `git` tool overlaps with nearly every specific git_* tool, so agents must guess whether to use the catch-all or a dedicated command. `git_checkout`, `git_switch`, and `git_restore` also have overlapping semantics, and `git_push` vs `git_push_new_branch` require careful reading to distinguish.

    Naming Consistency4/5

    All tools use a consistent git_ prefix and snake_case naming, making the set highly predictable. The lone exception is the generic `git` tool, which lacks a subcommand suffix and slightly breaks the pattern.

    Tool Count2/5

    27 tools is heavy for this domain, and many duplicate functionality already exposed by the generic `git` tool. The set feels bloated rather than well-scoped, with several niche subcommands included while other essential ones are missing.

    Completeness2/5

    For a server named git-remote-mcp, critical remote operations like fetch, pull, clone, and remote management are absent. Local coverage is broad, but the remote lifecycle is severely incomplete and will cause agent failures for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources