herdr-mcp
Related Servers
Alternatives to herdr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to list existing local terminal sessions, read current screen output, and send prompts to operator-approved terminals through an existing herdr-core Unix socket without starting or managing the core.MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to remotely control a running Herdr session: see agent status, arrange tabs and panes, start and prompt coding agents, and run worktree-isolated jobs over stdio or Streamable HTTP. Includes policy controls such as allowlists, read-only mode, disabled tools, and an audit log.322MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to use Desktop Commander tools locally over stdio or through an authenticated remote HTTP endpoint, including file, directory, search, document, process, and terminal-session operations.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to start and drive terminal processes, read and write files, make exact-match text edits, move files, inspect metadata, and paginate through local file-content searches. It also exposes configuration, prompt, usage and recent-call tools alongside those filesystem, search and process capabilities.87 npmMIT
- 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 gradedqualityBmaintenanceEnables MCP clients to remotely drive a vibeOS desktop, including reading the desktop, managing files, editing OS files, and executing commands in the VM.444 npmMIT
TDQS
Scored across 25 tools
Tools are well-differentiated: exec vs run (short vs long/interactive), read (screen) vs get (facts) vs file_read, and send (text) vs keys (named keys) have clear boundaries. The only mild overlaps are put vs file_write (file beside terminal vs atomic whole-file write) and app_do vs rpc, but descriptions draw the line.
Consistent herdr_ prefix with predictable verb_noun (herdr_file_read, herdr_app_do, herdr_kill). A few are nouns (herdr_templates, herdr_machines) for list-like resources, but the herdr_app_* family is grouped cleanly and no style mixing (camelCase) appears.
25 tools is at the heavy edge and spans several sub-domains (terminal control, file ops, app/window, machines, templates). Each earns its place, but some could consolidate (exec/run, app_ls/app_status), landing it borderline rather than well-scoped.
Strong lifecycle coverage: run/send/keys/interrupt/kill/rm/wait/read for terminals, full read/write/edit for files, plus window and machine introspection. A few operations (machine add/connect) are only reachable via herdr_rpc, but that escape hatch plus rpc.discover prevents dead ends.