F
licenseNot graded
qualityC
maintenanceEnables orchestrating multi-agent AI coding workflows with Git worktree isolation, parallel testing, and security scanning via the Model Context Protocol.
-
random-agent
by randomchips
Related Servers
Alternatives to random-agent
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceFacilitates autonomous AI agent collaboration on software projects through file-based task management and inter-agent communication via the Model Context Protocol.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceA production-grade multi-agent workflow orchestrator built on the Model Context Protocol, featuring planner/executor/critic agents, durable run state, and replayable traces.15MIT
- FlicenseNot gradedqualityBmaintenanceEnables collaborative software development through a team of specialized AI agents (Architect, Developer, Reviewer, Tester) communicating via the Model Context Protocol, with tools for file management, task tracking, and code review.-
- AlicenseNot gradedqualityCmaintenanceProvides structured workflows (phases, gates, coordination) for AI agents, enabling complex task execution with quality enforcement and multi-agent coordination via Model Context Protocol.2Apache 2.0
- FlicenseBqualityCmaintenanceEnables AI assistants to orchestrate multi-step workflows by converting natural language into executable plans, coordinating tools, agents, and services via the Model Context Protocol.4-
TDQS
B3.3/5.0
Scored across 8 tools
Disambiguation4/5
Tools are mostly distinct: metrics, status, and logs each read different data sources (DB, live coordinator state, files), while inject, orchestrate, handle_stuck, and coordinator manage different aspects of the system. However, metrics and status could be confused for overlapping system information.
Naming Consistency2/5
Tool names mix nouns (metrics, status, logs, coordinator) with imperative verbs (inject, handle_stuck, orchestrate, assert). There is no consistent verb_noun or noun_verb pattern, making the set feel ad hoc.
Tool Count5/5
Eight tools is well within the ideal 3-15 range for this domain. Each tool serves a distinct operational purpose without redundancy or bloat.
Completeness4/5
The set covers core operations: observability (metrics, status, logs), task injection, failure recovery, coordinator control, high-level orchestration, and assertion. Minor gaps exist (e.g., no direct task result retrieval outside orchestrate), but workflows are largely complete.
Maintenance
ActivityInactive
ResponsivenessNo issues