repopilot
Related Servers
Alternatives to repopilot
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEvidence-backed, read-only codebase diagnostics for coding agents: secrets, dependency, RLS, and source-impact audits with a verify loop and PR review verdicts. Never writes files or uses the network by default.7146 npmMIT
- AlicenseAqualityBmaintenanceEnables local, deterministic review of GitHub and GitLab pull request diffs for secret leaks, OWASP injection issues, WCAG 2.2 AA/EU EAA accessibility gaps, EU AI Act transparency, and database RLS risks, producing risk scores, merge decisions, committable suggestions, and SARIF exports.4MIT
- AlicenseAqualityBmaintenanceLocal code-graph engine for AI coding workflows: static analysis of Rust, Cangjie, ArkTS, TypeScript/JavaScript, C/C++, Python, and Shell projects into symbols, imports, call graphs, and quality gates, with pre-commit change review and impact analysis. Read-only by design — never executes build scripts or uploads code.61MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to audit git diffs, scan for leaked secrets and unsafe APIs, detect breaking changes, triage issues, generate changelogs, and assess repository hygiene through native stdio JSON-RPC tools.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query a local code graph over stdio, so they can see what a Git change may affect, find related tests, routes and nodes, and cite evidence paths — read-only and fully on-machine.2 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to turn local git history into answers about recent activity, file hotspots, change coupling, stale or already-merged branches, contributors, ref comparisons, and drafted release notes. It runs locally over stdio with a git subcommand allowlist, so it is read-only, works offline and without shell access, and is safe to auto-approve.13284 npmMIT
TDQS
Scored across 6 tools
The three top-level entry points are clearly distinct: repopilot_scan (health audit as JSON), repopilot_review_change (diff review), and repopilot_context (Markdown brief), and each description explicitly says when to prefer the others. The only soft spot is the trio of explanation tools, whose names (explain_finding vs explain_review_signal vs explain_file) are similar and whose correct choice depends on knowing whether you hold a finding_id, a signal_id, or a path — the descriptions do call this out, so misselection is unlikely but not impossible.
All six tools share a repopilot_ prefix and snake_case with a clear verb_ or verb_noun shape (review_change, explain_finding, scan). The only deviation is repopilot_context, which uses a bare noun rather than a verb, breaking the otherwise predictable pattern slightly. Still highly readable and consistent overall.
Six tools is well-scoped for a local repo audit/review server: three do the work (scan, review_change, context) and three provide explanation for the objects those produce. No tool looks like filler, and nothing essential appears to be collapsed into an overloaded god-tool.
The read/analyze/explain lifecycle is covered thoroughly: audit, change review, orientation brief, and explanation for findings, signals, and files. Minor gaps remain — there is no tool to inspect or manage configuration profiles/suppressions or to enumerate available rules/detectors in bulk, which an agent doing suppression cleanup would want. For a read-only analysis server, core workflows are not blocked.