Skip to main content
Glama
Sign In
CalebChen941028

hmesh-mcp

by CalebChen941028
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hmesh-mcp

No user-submitted related servers found.

    Related Servers

    • engineering-mcp

      yunuo110
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables repository-aware lifecycle management and controlled delegation of coding tasks to trusted worker harnesses via MCP, with execution isolation, recovery, and verified handoff.
      13 npm
      8
      Apache 2.0

    • Agent Harness Kit

      AndreasHart3607
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to run structured multi-agent workflows with shared documents, tracked tasks, handoffs, and health-gated completion evidence. It integrates with multiple coding tools while keeping task state, actions, and health results in the harness.
      29 npm
      MIT

    • agentbus

      vatsal191201
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coordinating Claude Code and Codex on one machine by fanning out tasks to multiple agents in isolated Git worktrees, comparing results, picking a winning candidate, and handing off work between harnesses. It provides MCP stdio tools, a CLI, and a local loopback web cockpit.
      Apache 2.0

    • sea-lite

      rafe-walker
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables parallel coding agents to coordinate through a fenced ticket queue with atomic claim-and-dispatch, lease-based locks, dependency-aware scheduling, typed links, batch ticket creation, and hash-chained history over a shared SQLite file.
      1,715 npm
      Apache 2.0
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action, and the three-phase integration flow (status → plan → install) is explicitly separated by read/write semantics. Minor ambiguity remains between get_quota_status and report_quota_status, since 'report' sounds like a read but actually mutates the circuit, and the model-information trio (discover_harness_models, list_harnesses, get_model_market) requires reading descriptions to separate cache reads from live discovery.

    Naming Consistency4/5

    The surface is overwhelmingly verb_noun snake_case (get_task_status, cancel_task, update_project_context) with clear read/write prefixes. Deviations are cosmetic: parallel_dispatch inverts the verb order, preview_routing lacks an explicit object, and discover_harness_models/get_model_market stretch the pattern without breaking it.

    Tool Count4/5

    18 tools sit at the high end of comfortable but each corresponds to a real operation across dispatch, quota, integration, model discovery and project context. Nothing looks like filler, though the set is broad enough that a controller may need a session to build a mental map.

    Completeness4/5

    Core lifecycle is well covered: routing preview, dispatch (single and parallel), status, cancel, patch application, quota read/write and integration detect/plan/install. Gaps are real but workaroundable: there is no list_tasks to enumerate tickets before calling get_task_status, no uninstall/ignore integration despite the 'ignored' state, and no tool to edit tier bindings that list_harnesses reports.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources