souschef
Related Servers
Alternatives to souschef
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables an agent to verify its own work mid-task by deliberately breaking each changed line, re-running the test suite in isolated workers, and reporting which breaks no test catches, along with a plan tool that previews which changed lines would be checked.MIT
- FlicenseNot gradedqualityDmaintenanceTransforms single-attempt coding into a multi-attempt, test-validated refinement loop by running your actual test suite and feeding failures back to the LLM as structured directives.3-
- AlicenseAqualityCmaintenanceEnables MCP clients to delegate routine coding tasks to a local model in isolated git worktrees, using test results as a gate and the client as the reviewer before changes are merged.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to deterministically audit test files for fake or fragile tests (no assertions, tautological or swallowed assertions, focused/skipped tests, fixed sleeps, real network calls) and to run the project's actual test runner, treating an exit-0 run with zero tests as a failure and flagging changed source files that lack test coverage.51 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to run a project's pytest, unittest, jest, or vitest suites and get back compact structured results with trimmed tracebacks, collection errors kept apart from real failures, and the slowest tests. Agents can then re-run just the failures, expand one failure with local variables, repeatedly execute a single test to judge flakiness, and inspect Python coverage gaps, all under a hard timeout that kills the whole process tree.7MIT
- AlicenseNot gradedqualityCmaintenanceTurns bounded coding tasks into reviewable Git diffs using isolated worktrees, configurable worker models, and test execution.MIT
TDQS
Scored across 7 tools
The tools have distinct primary roles: delegate_task starts a task, wait_for_task blocks, get_task_status gives a snapshot, get_task_result returns a final report, get_task_diff shows changes, cancel_task stops, and doctor checks setup. However, wait_for_task, get_task_status, and get_task_result all surface status or progress details, so an agent could occasionally choose the wrong one when checking on a task.
Most names follow a clear verb_noun snake_case pattern (delegate_task, get_task_result, etc.), but 'doctor' breaks the pattern as a bare noun with no verb. Still readable and mostly consistent.
Seven tools is well within the sweet spot for a task orchestrator; each covers a distinct lifecycle operation (start, monitor, result, diff, cancel, environment check) without bloat.
The surface covers the core lifecycle: delegation, blocking wait, status polling, result retrieval, diff inspection, cancellation, and environment diagnosis. Minor gaps exist—e.g., no tool to list tasks or retrieve a task by anything other than ID—but agents can work around these by tracking task IDs.