RMR
Related Servers
Alternatives to RMR
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables users to explore a local repository’s commit history through read-only MCP tools, including branch lanes, merge edges, branch selection, search highlighting, commit metadata, file statistics, and bounded patches.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect local Git repositories through five focused, read-only tools for repository trees, literal text search, numbered file reads, bounded git diffs, and project summaries while confining paths, skipping secret-like and binary files, and enforcing output limits.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract information from GitHub repositories, including repository summaries, project directory structures, and file contents. It integrates with gitingest to provide these capabilities.-
- AlicenseBqualityCmaintenanceEnables MCP clients to drive local Codex on a target Git repository: inspect repo state, start and follow up on tasks, review events and diffs, and record audit evidence for research governance.272MIT
- AlicenseAqualityCmaintenanceMCP server for git archaeology — churn hotspots, blame summaries, bus factor, commit forensics and file history over any local repository.113MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to inspect a single sandboxed project directory by listing files, reading UTF-8 text files, and viewing recent git history, while preventing writes, execution, or access outside that directory.MIT
TDQS
Scored across 4 tools
The four tools map cleanly to a tiered model (health check, Tier 1 overview, Tier 2 investigation, Tier 3 evidence), so the primary boundaries are clear. However, there is real overlap at the edges: 'symbol' appears both in investigate_codebase (definition + references) and inspect_evidence (read symbol with SHA-256 hash), and file listing in get_project_overview vs. file reading in inspect_evidence can be confused.
Three tools follow a verb-first snake_case pattern (get_project_overview, investigate_codebase, inspect_evidence), giving a predictable read/query convention. 'ping' is a bare verb and breaks the noun-phrase pattern, but as a single conventional health-check name it is a minor deviation.
Four tools is thin on the surface, and the real complexity is hidden inside investigate_codebase, which multiplexes seven modes (outline, symbol, grep, ast, callers, callees, impact) behind one name. This is efficient but pushes mode selection into parameters, making the effective toolset larger than four and harder to discover.
The read/investigation lifecycle is covered end to end, but the descriptions state that callers/callees/impact require a local CodeGraph index and no tool exists to build, refresh, or inspect that index — a dead end for an agent on a cold workspace. All tools are read-only, with no way to record findings, ADRs, or state.