Skip to main content
Glama
aelaguiz

herdr-mcp

by aelaguiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to herdr-mcp

No user-submitted related servers found.

    Related Servers

    • goose-herdr

      aquaherd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables goose to control the Herdr terminal workspace manager, allowing AI agents to inspect and manipulate workspaces, tabs, panes, run commands, and manage agent states.
      1
      MIT

    • herdr-mcp

      islam3zzat
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to orchestrate Herdr coding agents by wrapping its Unix-socket JSON-RPC API, providing tools for agent management, layout editing, and terminal interaction.
      -

    • HT MCP Server

      memextech
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to programmatically control interactive terminal applications through HT sessions, supporting session management, key sending, snapshots, and command execution.
      1
      MIT

    • terminal-driver-mcp

      funkyfunc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to spawn persistent terminal sessions, send keystrokes, read screen state, and assert output, allowing them to interact with stateful terminal applications like vim, htop, and gdb.
      5 npm
      MIT

    • Tmux MCP Server

      audibleblink
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage local tmux sessions, including creating and controlling sessions, windows, and panes, sending commands, and capturing terminal output.
      16
      6 npm
      Do What The F*ck You Want To Public
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action pairs (list_panes, list_agents, split_pane, close_pane, wait_agent, wait_for_output). The main ambiguity is among send_text, send_keys, run_command, and prompt_agent, since all deliver input to a pane; the descriptions largely clarify them, but an agent could still misselect send_text vs run_command or prompt_agent when composing an action.

    Naming Consistency5/5

    Almost every tool follows a clear verb_noun pattern: list_*, get_agent, prompt_agent, wait_agent, send_text, send_keys, run_command, split_pane, close_pane. The plural/singular list_* vs get_ is conventional and predictable, and there are no mixed casing or random names.

    Tool Count5/5

    14 tools is a well-scoped number for a terminal/agent-orchestration server. Each tool covers a meaningful operation without excessive redundancy or an overwhelming surface.

    Completeness4/5

    The surface covers orientation, reading output, sending input and keys, running commands, waiting for output/agent state, splitting panes, and closing panes—so core workflows are solid. The main gap is that there is no explicit way to create a new workspace or tab, only split an existing pane, which limits some session-management scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources