Workbuddy Local Worker
Related Servers
Alternatives to Workbuddy Local Worker
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables a main agent to delegate execution tasks to WorkBuddy through MCP, supporting multi-turn sessions, task status tracking, permission approvals, execution reports, and CLI fallback.1050 npm1MIT
- AlicenseNot gradedqualityCmaintenanceLets 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
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.-
- AlicenseAqualityBmaintenanceEnables 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.1235 npm7MIT
- AlicenseNot gradedqualityAmaintenanceA 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
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
TDQS
Scored across 7 tools
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.
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.
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.
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.