Skip to main content
Glama
haiyewei

mcp-server-grf

by haiyewei

Related Servers

Alternatives to mcp-server-grf

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Git repositories, enabling AI assistants to manage repositories, branches, commits, and files through a standardized interface.
      3,381 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants deep understanding of your local Git repositories, providing instant repo overviews, change summaries, blame analysis, changelogs, branch health checks, and history search.
      76 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      The Git MCP Server allows AI assistants to perform enhanced Git operations via the Model Context Protocol, supporting core Git functions, branch and tag management, GitHub integration, and more.
      21
      91 npm
      6
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that fetches documentation from public git repositories at specific versions, enabling AI coding assistants to access up-to-date, ref-pinned docs from source repos.
      5 npm
      2
      Apache 2.0

    TDQS

    D1.8/5.0

    Scored across 12 tools

    Disambiguation2/5

    With no descriptions at all, multiple tools have unclear boundaries: grf_get vs grf_loaded, grf_load vs grf_loaded, and grf_sync vs grf_sync_status are hard to distinguish without context. An agent would likely misselect among these retrieval/state/action tools.

    Naming Consistency4/5

    All tools use a consistent snake_case convention with the grf_ prefix. However, the pattern is not strictly verb_noun (e.g., grf_loaded, grf_sync_status are noun/adjective forms), so minor deviations exist.

    Tool Count4/5

    12 tools fall within a reasonable range for a server managing a resource with CRUD, lifecycle, sync, config, and branch operations. The count is not excessive, though without descriptions we cannot confirm every tool is non-redundant.

    Completeness4/5

    The tool names suggest coverage of CRUD (list, add, get, update, clean), lifecycle (load, unload, loaded), sync (sync, sync_status), config, and branch switching. Minor gaps like explicit delete or search may exist, but the surface appears largely complete for an inferred resource management domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues