A
licenseNot graded
qualityB
maintenanceEnables delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.
413 npm
MIT
workbuddy-delegate
Related Servers
Alternatives to workbuddy-delegate
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Codex to dispatch well-scoped development tasks to a remote CodeBuddy Code instance, specify model and reasoning effort, monitor progress, retrieve results, and review Git changes without auto-merging.3 npmMIT
- AlicenseBqualityDmaintenanceEnables coding agents like Claude Code and Codex to offload boilerplate generation, summarization, and other bounded text tasks to local or cheap cloud LLMs, keeping the frontier agent in charge of judgment and code edits.93MIT
- AlicenseAqualityBmaintenanceEnables Codex to delegate bounded code analysis, review, isolated edits, multimodal research, and native image generation to supervised Antigravity workers, with queued execution, retries, and inspectable patches.232MIT
- AlicenseNot gradedqualityCmaintenanceEnables Codex to delegate explicitly assigned subtasks to a local runtime that executes them with user-configured models such as DeepSeek, Qwen, or Claude. All project modifications are gated behind generated diffs and human approval before being applied.MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude Code or any MCP client to delegate bounded tasks such as code review, boilerplate, and documentation to local or cloud OpenAI-compatible LLMs. This reduces token usage by keeping large source files out of the main model's context while allowing results to be reviewed by the orchestrator.-
TDQS
A3.8/5.0
Scored across 5 tools
Disambiguation4/5
The tools are mostly distinct: status, plan, delegate, read_result, and usage each serve a clear purpose. However, 'workbuddy_plan' (classify eligibility) and 'workbuddy_status' (check limits) could be slightly confused as both are pre-flight checks, but descriptions clarify.
Naming Consistency4/5
All tools share the 'workbuddy_' prefix and use a consistent verb_noun pattern (status, plan, delegate_to, read_result, usage). 'delegate_to_workbuddy' is slightly more verbose but still fits the pattern, so minor deviation.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of managing delegation to WorkBuddy. Each tool covers a distinct aspect: status, planning, delegation, result reading, and usage tracking, which is appropriate.
Completeness4/5
The surface covers the main lifecycle: check status (status), eligibility (plan), delegate, read result, and usage. A minor gap is the lack of a cancel/abort tool for pending delegations, but the bounded tasks are short-lived, so this is not critical.
Maintenance
ActivitySlowing
ResponsivenessNo issues