herdr-mcp
Related Servers
Alternatives to herdr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to observe and control a running Herdr session by inspecting panes, agents, layouts, and live lifecycle events, and by prompting agents, waiting for completion, running commands, and managing workspaces, tabs, panes, and worktrees.411MIT
- AlicenseNot gradedqualityCmaintenanceLets MCP clients such as Claude Code, Cursor, and Claude.ai inspect and drive herdr workspaces, panes, and coding agents over a local socket, running either as a local stdio process or as an OAuth-protected HTTP endpoint published through a Cloudflare Tunnel. It exposes tools to create workspaces and tabs, split panes, start and prompt agents, read their output, and wait for results.MIT
- AlicenseNot gradedqualityBmaintenanceConnects remote AI agents and other MCP clients to a running Herdr session, enabling them to list terminal panes, check output, send tasks, and wait for status changes.5MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Grok Bot to inspect a running Herdr session through a strict read-only allowlist: listing active agents with their statuses and pane targets, checking a single agent's status, and reading bounded, redacted pane text. Connections run either locally on the Herdr host or over a locked-down SSH/Tailscale host alias, with prompts, keystrokes, focus changes, and arbitrary commands hard-denied.4MIT
- AlicenseNot gradedqualityCmaintenanceExposes typed MCP tools for driving herdr terminal fleets, letting an agent list, create, focus, and close workspaces, tabs, and panes, send text or key presses, and run commands locally or over remote machines. It also starts, prompts, waits on, renames, and reads AI agents, returning either raw pane output or a normalized structured transcript.12 npmMIT
- FlicenseAqualityDmaintenanceEnables coding agents to control and inspect a running Herdr terminal session, including listing workspaces, tabs, panes, and agents, reading pane output, prompting agents, sending keys and commands, waiting for output or state, and splitting or closing panes.14-
TDQS
Scored across 32 tools
Most tools target a distinct resource+action (agent_*, pane_*, tab_*, workspace_*, worktree_*), so the majority are easy to tell apart. However, several pairs have subtle boundaries: herdr_open_agent vs herdr_agent_start vs herdr_job_start all launch agents, and herdr_agent_read/herdr_pane_read and herdr_agent_wait/herdr_pane_wait_output differ only by target. The descriptions usually clarify the intent, keeping overlap manageable.
The dominant pattern is herdr_<resource>_<action> (pane_split, agent_prompt, tab_create), applied consistently across most tools. Deviations exist: list operations use bare plurals (herdr_agents, herdr_panes, herdr_tabs, herdr_workspaces) while worktrees break the mold with herdr_worktree_list, and herdr_open_agent flips to verb_noun ordering. Still largely readable and predictable.
32 tools is heavy, exceeding the comfortable range, though the domain (a terminal/agent multiplexer spanning workspaces, tabs, panes, agents, worktrees, and jobs) genuinely justifies broad coverage. Several tools could plausibly be consolidated or folded into parameters. Borderline rather than egregious.
The surface covers create/list/close across workspaces, tabs, panes, and worktrees, plus rich agent lifecycle (start, prompt, read, wait, rename, focus, explain) and a high-level status snapshot. Minor gaps remain, such as no explicit agent stop/kill and no rename/move for workspaces or tabs. Core lifecycle workflows are covered without dead ends.