mcp-server-grf
Related Servers
Alternatives to mcp-server-grf
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn 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 npm1Apache 2.0
- AlicenseBqualityCmaintenanceAn enhanced Git MCP server that provides AI assistants with powerful code review, commit analysis, and branch management capabilities for Git repositories.534 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server enabling AI assistants to understand GitLab repositories through on-demand source code analysis using specialized AI agents.-
- AlicenseNot gradedqualityDmaintenanceAn 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 npmMIT
- FlicenseBqualityDmaintenanceThe 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.2191 npm6-
- AlicenseNot gradedqualityCmaintenanceMCP 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 npm2Apache 2.0
TDQS
Scored across 12 tools
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.
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.
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.
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.