local-delegate
Related Servers
Alternatives to local-delegate
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server connecting Claude Code to LM Studio, delegating token-expensive tasks to a local model while keeping the cloud model in control. It reduces cloud context usage by reading files locally and returning only the processed results.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to delegate mechanical tasks (summaries, boilerplate, reformatting) to local models running in LM Studio.1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that delegates mechanical tasks like summarization, classification, extraction, and drafting to a local Llama.cpp LLM, serving as a cost-optimization layer while Claude handles reasoning and quality control.MIT
- AlicenseAqualityBmaintenanceEnables Claude to offload bulk reading, first-draft writing, and mechanical edits to a local or OpenAI-compatible model, with code-enforced verification, staged patches, project checks, and token budgets to save tokens and cost.8MIT
- AlicenseBqualityDmaintenanceDelegates heavy, repetitive, and verifiable tasks like PDF extraction, code analysis, and log processing to a local LLM to reduce token consumption for frontier AI models, while keeping decision-making with the main AI.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to offload noisy commands, large files, and web research to a local OpenAI-compatible LLM, receiving only concise cited answers instead of the raw material. It also optionally delegates writing a single file inside an isolated git worktree, retrying until a Claude-authored test passes.58 npm2MIT
TDQS
Scored across 11 tools
Each specialized tool maps to a distinct task type (extract, summarize, translate, classify, explain, commit message, lint log, image description, boilerplate generation), and the descriptions draw those lines explicitly. The only real overlap is `local_delegate`, a general text->text escape hatch that can do much of what summarize/translate/explain_code do, but its description states 'use it when no specific tool fits' and warns about chunking misuse, which mitigates selection errors.
All 11 tools share a `local_` prefix with snake_case names, giving a strongly predictable family. Minor deviation: most names are verb-style (`local_extract`, `local_summarize`, `local_translate`), while `local_commit_msg` and `local_status` are noun-phrase, and `local_delegate` is the vague generic sibling of the `local_*` prefix itself.
11 tools sits squarely in the well-scoped range and each one targets a recognizable delegation niche (structured extraction, summarization, translation, classification, code explanation, commit drafting, log triage, vision, codegen, diagnostics, generic fallback). Nothing feels padded, and the single generic tool avoids a combinatorial explosion of one-off variants.
For a 'keep work out of Claude's context' server, the surface covers the main offload patterns plus a status/diagnostics tool and a generic fallback for unforeseen tasks, so agents are rarely at a dead end. Gaps are minor and arguable (no dedicated review/diff-analysis or batch/multi-file driver), and the fallback tool plus `local_status` model introspection largely compensates.