Skip to main content
Glama
kevmo314

herdr-mcp

by kevmo314
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to herdr-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      2
      MIT

    • herdr-mcp

      frysquint
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      41
      MIT

    • vibeos-mcp

      caffeinum
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to remotely drive a vibeOS desktop, including reading the desktop, managing files, editing OS files, and executing commands in the VM.
      475 npm
      MIT

    • ssh-mcp

      YUChoe
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP clients with a persistent SSH shell on legacy Unix hosts, including session management, SFTP file transfer, and ClearCase workflow helpers.
      13,102 npm
      MIT

    • cowbell

      WSHAPER
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 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.
      4 npm
      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.5/5.0

    Scored across 25 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources