A
licenseNot graded
qualityD
maintenanceEnables real-time communication and orchestration of multiple AI agents with a web dashboard for monitoring agent activities, tasks, and artifacts.
MIT
peon-orchestrator
by prmgint
Related Servers
Alternatives to peon-orchestrator
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to delegate tasks, run adversarial reviews, and manage background jobs across multiple models and providers via anymodel_* tools.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables persistent task and goal management with AI-powered decomposition, cross-session continuity, and fault-tolerant multi-agent pipelines.1-
- AlicenseNot gradedqualityBmaintenanceEnables coordinating specialist agents through an event-driven backend, allowing submission of goals, retrieval of job status and results, and listing of jobs via MCP tools.MIT
- AlicenseCqualityCmaintenanceEnables durable, queryable multi-agent coordination with non-blocking peer messaging, task leases, and campaign-governed collaboration across sessions.59MIT
- AlicenseBqualityDmaintenanceEnables AI agents to orchestrate a team of sub-agents through tmux sessions for complex task delegation and parallel implementation. It provides tools for launching agents, monitoring their real-time status, and managing communication between them.67 npm26MIT
TDQS
B3.2/5.0
Scored across 14 tools
Disambiguation4/5
Most tools are clearly distinct: agent lifecycle tools (list, spawn, stop, status) and task tools (assign, status, result, aggregate) separate cleanly. Minor overlap exists between list_agents and agent_status since list_agents already includes status fields, but descriptions clarify the singular focus of agent_status. Storage tools are unambiguous.
Naming Consistency3/5
Naming mixes conventions: verb_noun (list_agents, spawn_agent, assign_task, read_storage, write_storage, aggregate_results), noun_noun (task_status, task_result, agent_status), and single verb (broadcast). While readable, the pattern is not uniform and violates expectations (e.g., agent_status vs status_agent, storage_cleanup vs cleanup_storage).
Tool Count4/5
14 tools is within a reasonable range for an orchestrator covering agent lifecycle, task management, and shared storage. Each tool serves a distinct purpose and the count reflects the breadth of functionality without being excessive.
Completeness4/5
The tool surface covers core workflows well: agent creation/listing/removal/status, task assignment/tracking/results/aggregation, and storage read/write/cleanup. Minor gaps like a direct task cancellation or agent update are missing, but these are edge cases not fundamental to the domain.