Skip to main content
Glama

Related Servers

Alternatives to workbuddy-ai

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      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
      309 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      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
      B
      maintenance
      Enables a supported web-chat AI client to control a local Windows computer through MCP using explicit, user-authorized tool calls for file, browser, shell, Git, and optional desktop operations.
      MIT

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: listing available models, performing a chat completion, and checking account/connection status. No overlap in operation or expected inputs, so an agent can easily select the right tool.

    Naming Consistency5/5

    All tools use the same `wb_ai_` prefix followed by a concise noun describing the resource or action. The pattern is predictable and readable, with no mixed casing or verb-style inconsistencies.

    Tool Count5/5

    Three tools is a well-scoped minimal surface for an AI gateway wrapper: discovery, execution, and status/authentication. Each tool earns its place, and there is no redundant or thin filler.

    Completeness4/5

    The core lifecycle for using the service is covered: discover models, invoke a model, and verify connection/credits. Minor gaps exist around explicit login/token refresh and multi-turn conversation management, but these are not required for the stated one-shot completion purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data