A
licenseNot graded
qualityA
maintenanceEnables AI coding providers to run structured multi-agent workflows with specs, tracked tasks, handoffs, health gates, and audited repair mode.
29 npm
MIT
agent-work-mcp
by yurikaza
Related Servers
Alternatives to agent-work-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with shared documents, tracked tasks, handoffs, and health-gated completion.29 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with use cases, specifications, tracked tasks, handoffs, and health-gated completion.-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with document drafting, task tracking, handoffs, and health-gated completion.29 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with shared use-case and spec documents, tracked tasks, handoffs, health checks, and review/repair gates.29 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding providers to run structured multi-agent workflows with specifications, tracked tasks, handoffs, approvals, and health-gated completion across supported coding environments.29 npmMIT
TDQS
A4.1/5.0
Scored across 16 tools
Disambiguation5/5
Each tool targets a distinct aspect of session and work-graph management, with clear separation between session lifecycle (start/pause/resume/stop), state inspection (get_session, get_phase, get_handoff, get_session_report), work graph manipulation (get/update_work_graph, next/report_work), and decision handling (request/get/record_decision). No two tools appear to do the same thing.
Naming Consistency5/5
All 16 tools follow a consistent snake_case verb_noun pattern (e.g., pause_session, update_work_graph, request_decision). The verbs are imperative and match the action taken, with no mixing of conventions or vague generic names.
Tool Count4/5
At 16 tools, the set is slightly above the typical 3–15 range, but each tool serves a distinct and necessary function for managing complex agent work sessions, covering lifecycle, graph, decisions, and reporting. The count feels justified rather than bloated.
Completeness5/5
The tool surface fully covers the session lifecycle (start, pause, resume, stop), work graph operations (create/update, query, claim, report), decision management (request, query, record), and reporting (handoff, session report). No obvious dead ends or missing operations for the stated domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues