Skip to main content
Glama
cafitac

HermitAgent

by cafitac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to HermitAgent

No user-submitted related servers found.

    Related Servers

    • dsh-mcp

      Mr-potato-123
      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.
      246 npm
      117
      MIT

    • Fagan

      motock
      A
      license
      A
      quality
      A
      maintenance
      Autonomous coding pipeline exposed as an MCP server: plan, dispatch, review, and merge software stories through worktree-isolated agents. A frontier model (Claude) handles judgment — planning, review, risk adjudication — while a local model does the implementation, gated by TDD and a merge-time test rerun on the rebased branch.
      25
      5
      Apache 2.0

    • ForgeMCP

      Tz22z
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables autonomous software-engineering tasks in a repository by coordinating filesystem, GitHub, database, and CI/CD tools through MCP, with a deterministic safety boundary for permissions, validation, timeouts, duplicate protection, and test verification.
      MIT

    • Jev Reflex

      xnuonux
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to make small, bounded decisions around tasks via stdio MCP, supporting source-bound context, durable budgets, bulk jobs, and measured outcomes while leaving planning and reasoning with the main model.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources