Skip to main content
Glama
sunnyvempati

herdr-mcp

by sunnyvempati
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to herdr-mcp

No user-submitted related servers found.

    Related Servers

    • herdr-mcp

      aelaguiz
      F
      license
      A
      quality
      B
      maintenance
      Enables 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
      -

    • 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.
      -

    • goose-herdr

      aquaherd
      A
      license
      Not graded
      quality
      D
      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.
      3
      MIT

    • herdr-mcp

      thomasfossum
      A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      32
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: status check, lists for workspaces/tabs/panes, and agent-specific operations (list, get, read, wait). The list/read/wait agent tools are clearly differentiated by their descriptions, so an agent can easily choose the right one.

    Naming Consistency4/5

    Almost all tools follow a consistent herdr_ prefix and noun_verb pattern (e.g., herdr_workspace_list, herdr_agent_get). The only deviation is herdr_status, which lacks a verb, but it remains readable and predictable overall.

    Tool Count5/5

    8 tools is a well-scoped set for a monitoring-focused server. Each tool earns its place by covering a distinct resource or agent operation without redundancy.

    Completeness4/5

    The surface covers listing workspaces, tabs, panes, and agents, plus detailed agent monitoring (get, read, wait) and server status. However, it lacks get operations for workspaces, tabs, or panes, and offers no control actions (e.g., create, close, start agent), which are minor gaps for a monitoring server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources