A
licenseA
qualityA
maintenanceA local MCP server that exposes Bazel build system capabilities to AI assistants.
8
2
MIT
gavel
Officialby gavelcode
Related Servers
Alternatives to gavel
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.23 npmMIT
- AlicenseNot gradedqualityCmaintenanceThin MCP server wrapping the Gemini CLI for AI assistants, supporting workspace-aware multi-repository analysis and forward-compatible flags.MIT
- AlicenseNot gradedqualityBmaintenancePrivate, local-first code intelligence MCP server that builds a static graph of repositories and exposes search, architecture, impact analysis, and review tools via MCP.MIT
BuildPulse MCPofficial
AlicenseNot gradedqualityAmaintenanceMCP server for the BuildPulse Platform API. Lets AI agents surface flaky tests, CI run history, and coverage health.MIT- FlicenseNot gradedqualityBmaintenanceMCP server that provides code intelligence by indexing configured repositories, extracting deterministic facts, and enabling graph queries, drift checks, and maps via Kuzu-backed MCP tools.-
TDQS
A3.8/5.0
Scored across 8 tools
Disambiguation4/5
Most tools map cleanly to distinct concerns: architecture, coverage, project-wide findings, single-file linting, initialization, validation, judgment, and trends. The only minor overlap is between gavel_findings and gavel_lint_file, but their project-wide vs. per-file scope is clearly differentiated.
Naming Consistency3/5
All tools share the consistent gavel_ prefix and snake_case style, but the second element mixes nouns (arch, coverage, findings, trends) with verbs (init, judge, validate, lint_file). This is readable and predictable at the prefix level, but it does not follow a uniform verb_noun convention.
Tool Count5/5
Eight tools is well within the ideal range for a focused static-analysis quality-gate server. Each tool addresses a meaningful part of the workflow without feeling padded or redundant.
Completeness5/5
The toolset covers the full expected lifecycle: setup with init, structural setup checks with validate, running the quality gate with judge, and accessing the main analysis outputs for coverage, lint findings, architecture violations, and historical trends. There are no obvious missing operations that would leave an agent stuck.
Maintenance
ActivitySlowing
ResponsivenessNo issues