Skip to main content
Glama

Related Servers

Alternatives to Workbuddy Local Worker

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets a lead MCP client delegate text tasks to other LLMs and run CLI coding agents as background jobs, exposing tools to list workers, ask a model synchronously, and check status, read results, or cancel long-running tasks.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents like Claude Code, Codex, Cursor, and OpenCode to delegate tasks to the WorkBuddy CLI as a sub-agent via an MCP tool, with one-command setup and configurable model/permission options.
      1
      235 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A stdio MCP server that lets any MCP client dispatch tasks to the local WorkBuddy desktop agent, wait until a run reaches a terminal state, and independently verify evidence such as session transcripts, tool-call counts, and archived copies. It also exposes read-only tools for locating WorkBuddy projects and sessions, publishing runs into the desktop app's workspace, and inspecting scheduled automation tasks, their run history, and overall scheduler health.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.
      1 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: send_message starts or continues work, stop_task cancels, and the select_* tools configure model or MCP/skills. However, get_message, wait_for_message, and get_status overlap somewhat in observing task events and pending input, which could require careful reading of descriptions to choose correctly.

    Naming Consistency5/5

    All seven tools follow a consistent snake_case verb_noun pattern such as send_message, get_status, stop_task, and select_model. The naming is predictable and easy to map to actions.

    Tool Count5/5

    Seven tools is well-scoped for an asynchronous worker interface covering task messaging, observation, cancellation, and configuration. Each tool appears to earn its place without obvious redundancy.

    Completeness5/5

    The surface covers the full interaction lifecycle: starting/continuing tasks, reading incremental events, waiting for events or input, checking health/status, cancelling tasks, and selecting runtime model and MCP/skill configuration. No obvious operational gaps are apparent for a local async worker.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues