squad-mcp
Related Servers
Alternatives to squad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for AI agents to classify changes into autonomous or human review lanes, and to run shadow simulations over backlogs without shipping anything.MIT
- AlicenseBqualityCmaintenanceEnables MCP-capable coding agents to obtain structured TypeSafe Jev decisions on code, diffs, debugging hypotheses, test failures, and bug reports through six review and triage tools. It returns categorized verdicts, severities, and probabilities rather than explanations or patches, leaving verification to the connected agent.61MIT
- AlicenseAqualityBmaintenanceOfficial Codna MCP server with Mojo-powered risk simulation. Maps repos with zero LLM tokens. 5 stdio tools: triage, root-cause analysis and fix plans (optional PRs), SARIF reachability proof, on-device code memory and bug reporting. Introspection needs no credentials; execution requires a one-time free codna login. Source: cli/codna/mcp_server.py. Registry: io.github.thyn-ai/codna.5538 PyPIApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables code agents to run risk-based Jev quality reviews on focused diffs through a read-only MCP tool, returning structured scores and weakness hints without modifying code.MIT
- AlicenseNot gradedqualityAmaintenanceAI code reviews and git activity digests with machine-readable risk scoring, available as an MCP server for use within an agent session.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.3 npm2MIT
TDQS
Scored across 27 tools
Tools are mostly distinct with detailed descriptions, but some orchestration tools like compose_squad_workflow and compose_advisory_bundle could be confused by an agent as they both aggregate pipelines. Overall, the purpose of each tool is well-defined.
All tools follow a consistent verb_noun pattern (e.g., detect_changed_files, record_learning), with no mixing of conventions. Naming is predictable and intuitive.
With 27 tools, the server is on the heavy side but justifiable given the complex domain of squad-based code review and workflow management. A smaller set could cover core functionality, but the current count reflects comprehensive coverage.
The tool surface covers nearly all aspects of the squad workflow: config, file detection, agent selection, task management, learning, run tracking, and advisory composition. Minor gaps like external notifications are acceptable given the scope.