herdr-mesh
Related Servers
Alternatives to herdr-mesh
No user-submitted related servers found.
Related Servers
- FlicenseAqualityAmaintenanceEnables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.143-
- AlicenseNot gradedqualityBmaintenanceEnables provider-neutral durable coordination for coding agents sharing Git work, including peer discovery, durable messaging, job progress tracking, and FIFO integration authority with fenced leases.MIT
- AlicenseBqualityAmaintenanceEnables multiple coding agents sharing one repository to coordinate their work through time-limited directory and file leases, an enforced pre-tool-use hook, shared presence tracking, messaging, and an audit history, so they never edit or run each other's files concurrently.1547 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to spawn, monitor, and control CLI coding agents running in isolated tmux sessions, with verified input injection, redacted pane capture, fleet and per-session state classification, lineage tracking, blocking exec with exit codes, cross-agent messaging, waste analytics, and log/ledger reading. Ownership checks, policy controls, and audit events keep every control action safe by default.7 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables parallel AI coding agents to claim files atomically, detect and prevent workspace collisions, and receive deterministic zero-latency safety verdicts on destructive shell commands without any network egress. It also provides autonomous wave dispatch, worker recovery, and completion verification for multi-agent workflows via a shared coordination board.713 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to securely inspect and edit approved code, use semantic code intelligence, run builds/tests, supervise bounded processes, inspect Git, and execute owner-approved SSH commands on engineering workstations.2Apache 2.0
TDQS
Scored across 44 tools
Most tools target distinct lease, agent, or handoff concerns, but several families overlap: three agent-wait variants, relay/handoff/batch_handoff, agent_read vs pane_read, and multiple cleanup/reconcile tools. The detailed descriptions help, but an agent must read closely to avoid selecting the wrong tool.
The dominant pattern is herdr_<object>_<action> (agent_list, controller_acquire, owned_worker_release), but there are notable exceptions like relay, handoff, batch_handoff, collect_handoffs, and wait_output, plus noun-style names like bridge_status and integration_status. The herdr_ prefix and snake_case keep it readable, but the convention is mixed.
44 tools is well above the threshold for a focused server and feels heavy for what is ultimately one orchestration domain. Many tools could be consolidated, such as the three agent-wait variants, multiple handoff submission/collection modes, and the various list/status/cleanup helpers.
The surface covers the core lifecycle well: controller leases, worker/reviewer leases, handoffs, agent inspection, and pane/tab/workspace discovery all have appropriate operations. Minor gaps exist around general pane writes or workspace/session mutation, but those appear intentionally outside the safety-focused lease model.