Skip to main content
Glama

Related Servers

Alternatives to HermitAgent

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets Claude Code or any MCP client hand bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model, an OpenAI-compatible endpoint, a router, or a cheap cloud API, so those files never enter the orchestrator's context window. This cuts token spend and quota use while providing a second model to sanity-check results.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code to hand bounded work — code reviews, boilerplate, commit messages, format conversion, embeddings — to a local or cloud OpenAI-compatible LLM instead of the main model, cutting token spend by keeping large files out of the orchestrator's context. It also provides a cheap second model for reviewing code and verifying results.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients like Claude Code to delegate bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model or a cheaper cloud endpoint, keeping large file contents out of the orchestrator's context window. This cuts token costs dramatically while providing a second model for independent review.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A cheap, fast execution layer for MCP agents that delegates file reads, edits, and command runs to a local DeepSeek Harness, reducing cost and latency while keeping the parent agent in control of planning and reasoning.
      225 npm
      116
      MIT

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle action: start (run_task), respond to prompts (reply_task), poll status (check_task), and abort (cancel_task). There is no functional overlap between them.

    Naming Consistency5/5

    All four tools follow the same verb_task pattern (run, reply, check, cancel). The naming is predictable and makes the API easy to navigate.

    Tool Count5/5

    Four tools is well-scoped for an async agentic task runner. Each tool earns its place and the surface is neither bloated nor thin.

    Completeness4/5

    The core lifecycle is covered: launch, interact, poll, and cancel. However, the needs_review state lacks an explicit approve/resume action, and completed tasks are not retrievable after removal, which are minor gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues