Skip to main content
Glama
kazuki0529

git-readonly-mcp

by kazuki0529
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to git-readonly-mcp

No user-submitted related servers found.

    Related Servers

    • git-history-viewer

      peekaboo-develop
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server that provides read-only access to Git repository history, exposing commit metadata and optionally content patches via configurable policies, with optional AI-powered analysis while never modifying Git state.
      13 npm
      Apache 2.0

    • otama

      Ronith2906
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI assistants safely access local git repositories, with free reads and gated writes requiring explicit confirmation.
      1
      MIT

    • weavatrix-git

      Weavatrix
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for fast, bounded, read-only Git evidence, enabling AI agents to query commit history, diffs, status, and snapshots by parsing repository storage directly.
      345 npm
      MIT

    • github-assistant-mcp

      imshashwatsingh
      F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.
      5
      -

    • TimeVerse Code Reader

      elimyliu
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server for code reading with intelligent caching, line-range selection, and language detection, enabling AI assistants to efficiently and safely explore file systems.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct read-only Git operation: history, diffs, blame, search, refs, file access, and remotes. Potentially similar tools like diff vs range_diff and log vs show_commit are clearly separated by their descriptions and expected usage.

    Naming Consistency5/5

    All tool names follow the consistent git_ prefix with a verb_noun pattern in lowercase snake_case. Composite names like list_remote_refs and range_diff are predictable extensions of the established convention.

    Tool Count5/5

    Fifteen tools is at the high end of the ideal range, but each tool covers a distinct capability needed for comprehensive read-only Git inspection. No tool feels redundant or ornamental.

    Completeness5/5

    The surface covers repository discovery, status, history, commit inspection, diffs, blame, search, refs, tree browsing, file reading, comparison, and remote inspection. For a read-only Git server, this is a complete and coherent feature set with no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources