A
licenseNot graded
qualityA
maintenanceCoordinates parallel AI coding agents by providing task ownership, scoped file locks, handoffs, and verification workflows.
MIT
tianshu-mcp
by lanlan0811
Related Servers
Alternatives to tianshu-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables delegating asynchronous coding tasks and DAG workflows to local Oh My Pi (OMP) CLI sub-agents, with topological orchestration, path isolation, and supervised resumption.943 npm1MIT
- 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
- AlicenseAqualityDmaintenanceMulti-agent orchestration server that enables parallel task delegation, sequential pipelines, cron scheduling, and cross-model peer review via CLI providers like Codex, Antigravity, OpenCode, and Claude Code.4216 npm5MIT
- AlicenseAqualityCmaintenanceA task-based AI orchestrator that bridges AI models (Gemini, Claude, OpenAI) with local environments, operating as an interactive CLI and an MCP server for structured autonomous development.25 npmMIT
- AlicenseAqualityBmaintenanceA task-level STDIO MCP server that lets Codex or any other MCP client hand off scoped coding jobs to an asynchronous worker agent which reads the code, edits files, and runs tests, while the client keeps ownership of planning and acceptance. Exposes submit, wait, query, follow-up, and cancel tools so multiple clients can queue and monitor tasks against a chosen project root.51MIT
TDQS
A3.7/5.0
Scored across 11 tools
Disambiguation4/5
Most tools have clear boundaries: task lifecycle (run/cancel/continue/rework/query/list/verify) vs. visual baseline (prepare/approve) vs. report/profile. The only mild overlap is verify_task vs. get_task_report (both relate to acceptance), but verify runs a new check while get_task_report reads an existing report.
Naming Consistency4/5
Tool names mostly follow a verb_noun pattern (get_task_report, prepare_visual_baseline, approve_visual_baseline, cancel_task, continue_task, list_tasks, query_task, rework_task, verify_task). Minor inconsistency: run_task is verb_noun but get_profiles is verb_noun too; all are snake_case and readable. The slight mix of 'task' vs 'tasks' (list_tasks plural vs others singular) is a small deviation.
Tool Count5/5
11 tools is well within the ideal 3-15 range and each tool maps to a distinct operation in the task-management and visual-baseline workflow. The count feels appropriate for the server's purpose: task lifecycle management plus baseline approval.
Completeness4/5
The task lifecycle is well covered: create (run_task), query (query_task/list_tasks), cancel, continue, rework, verify, and report retrieval. Minor gaps: no explicit delete/archive task tool, and visual baseline has prepare/approve but no explicit reject or list-baselines tool, though these may be intentionally omitted.
Maintenance
ActivityMaintained
ResponsivenessResponsive