Skip to main content
Glama
liuqianworkbuddy

wb-mcp

by liuqianworkbuddy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to wb-mcp

No user-submitted related servers found.

    Related Servers

    • Codex Harness MCP

      2091k
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI clients to invoke CLI-driven agent tools over Streamable HTTP, including shell execution, file operations, patching, image viewing, web search, and nested agent tasks, with permission modes and real-time progress streaming.
      -

    • workbuddy-mcp

      LinHaiJ
      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
      212 npm
      7
      MIT

    • m-tunnel

      mxyhi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables ChatGPT, Claude, and other web MCP clients to access and operate multiple VS Code workspaces through tools such as read, bash, edit, write, and workspace_info, with per-workspace tokens and role-based permissions.
      MIT

    • Sovereign Copilot MCP Server

      glatinone
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to expose temporal architectural memory, privacy sanitization, and local test-runner capabilities as MCP tools so clients like Claude Desktop, Cursor, and Hermes Agent can query decisions, sanitize prompts, and verify code changes.
      MIT

    • Remote MCP AuthKit Server

      kevinoneill
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote MCP client connections with WorkOS AuthKit authentication and organization-based permission controls. Demonstrates permission-gated tool access, such as image generation tools restricted by user permissions.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation2/5

    Several tools overlap in scope: wb_todo, wb_todo_done/edit/tag/del, and wb_add/wb_manage all cover todo creation/editing, while wb_dev_task duplicates wb_dev_task_create/stage/item. The read-only domains (wb_query, wb_vault, wb_archive) are clear, but the write-side boundaries are fuzzy enough to cause misselection.

    Naming Consistency3/5

    Most specific operations follow wb_<domain>_<action> (wb_todo_edit, wb_note_add), and the wb_ prefix is consistent. However, broad domain tools use bare nouns (wb_todo, wb_fin, wb_vault) and some tools use verb-first or abbreviated forms (wb_query, wb_add, wb_manage, wb_del), creating a mixed convention.

    Tool Count3/5

    At 20 tools, the server is at the high end of acceptable and feels heavy because many tools duplicate functionality covered by broader domain tools. A leaner set could drop or merge the generic wb_add/wb_manage with the specific add/done tools, but the count is not extreme.

    Completeness4/5

    Core workflows are covered: todo CRUD, note add/edit, schedule creation, idea capture, dev-task pipeline stages, and read-only vault/archive access. Minor gaps exist (no explicit note delete or dedicated schedule update/delete tool, finance operations hidden behind wb_fin), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources