Yevgeny
Related Servers
Alternatives to Yevgeny
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityCmaintenanceDelegates 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 gradedqualityFmaintenanceEnables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents like Claude Code or Codex to delegate tasks to a DeepSeek Harness subagent with its own context window, providing tools for task delegation, result waiting, continuation, and supervision with sandboxed execution.6MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to hand off bulk, mechanical, read-heavy tasks to a local model, including agentic loops that can read, write, and run commands sandboxed at zero cloud token cost.MIT
- AlicenseNot gradedqualityAmaintenanceEnables a coding agent such as Codex or Claude Code to delegate work to a local Pi coding-agent session, including second-opinion reviews, bulk reading kept out of the main context, and follow-up turns that retain context. Operators control what is possible by defining workspace and execution-profile aliases in a local config file, so clients cannot choose directories, models, providers, or permission levels themselves.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: direct one-turn ask, async delegated job lifecycle (start, status, result, cancel), and health check. delegate_status and delegate_result are separated by live progress versus final output, so there is no real ambiguity.
The delegate_* tools follow a consistent and predictable prefix pattern. ask and yevgeny_health deviate slightly from that convention, but they are readable and clearly labeled, so the overall naming remains coherent.
Six tools is a well-scoped set for a local-agent delegation server. Each tool maps to a necessary operation: direct ask, job start, status polling, result collection, cancellation, and health checking, with no redundant entries.
The tool set covers the full delegated-job lifecycle: start, monitor, collect, and cancel, plus a direct quick-ask path and a health check. Background process handling is also addressed through cancel and status. There are no obvious dead ends for the stated purpose.