herdr-mcp
Related Servers
Alternatives to herdr-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables 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-
- FlicenseAqualityBmaintenanceMCP server that exposes the Herdr terminal API as callable tools, enabling AI agents to manage terminal workspaces, tabs, panes, and agents. It dynamically generates tools from the Herdr API schema and communicates via Unix socket.20-
- AlicenseNot gradedqualityBmaintenanceEnables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.MIT

herdr-mcp-serverofficial
AlicenseNot gradedqualityCmaintenanceEnables a chat or voice assistant to drive coding agents running in herdr: it can start an agent on a task, list and watch sessions started anywhere, send follow-ups, answer an agent's questions and approve or refuse its permission prompts. Long-running work is reported back through webhook callbacks so the conversation can continue without blocking.MIT- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI clients to invoke CLI-driven agent tools over Streamable HTTP, including shell execution, file operations, patching, image viewing, web search, and nested agent tasks, with permission modes and real-time progress streaming.-
- AlicenseNot gradedqualityAmaintenanceEnables external MCP clients to drive DeepSeek Harness agents for real coding tasks, providing tools for task execution and queueing, session management, sandboxed file access, preset switching, and usage statistics.564 npm5GPL 3.0
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.