Skip to main content
Glama
Sign In
wolbarg

Wolbarg Coordination for Cursor

by wolbarg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Wolbarg Coordination for Cursor

No user-submitted related servers found.

    Related Servers

    • wb-cursor-bridge

      jsyzc2019
      A
      license
      A
      quality
      B
      maintenance
      Enables a supervisor agent to dispatch, monitor, follow up on, cancel, and inspect Cursor CLI code tasks through a governed MCP interface, with permission tiers, workspace allowlists, isolated git worktrees, and auditable artifacts. It also exposes an A2A-compatible HTTP endpoint for agent discovery and scheduling.
      9
      MIT

    • Agent Harness Kit

      oSahu48
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to run structured multi-agent workflows with tracked tasks, specifications, handoffs, and health-gated completion. It exposes MCP tools for task claiming, action logging, repairs, document validation, and lifecycle evidence.
      29 npm
      MIT

    • Agent Harness Kit

      Suzuki1440
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to run structured multi-agent workflows with document-backed specifications, tracked tasks, handoffs, health gates, and completion evidence. It exposes MCP tools for coordinating use cases, specs, implementation, review, and repair across supported providers.
      29 npm
      MIT

    • Agent Harness Kit

      Ngoc7225
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      MIT
    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

    D1.6/5.0

    Scored across 4 tools

    Disambiguation1/5

    All four tools effectively serve the same purpose: reporting that Wolbarg is not initialized. They overlap completely, making it impossible for an agent to distinguish meaningful differences.

    Naming Consistency1/5

    Tool names follow no consistent pattern: mixed lowercase with underscores (wolbarg_init_required, coordination_status), compound words (workspace_briefing), and verb-object (claim_scope). No uniform style or structure.

    Tool Count1/5

    Four tools are excessive for a single, trivial function (indicating uninitialized state). One or two tools would suffice; this count wastes surface area and confuses agents.

    Completeness1/5

    The tool surface covers only the uninitialized state and provides no actual coordination functionality. If Wolbarg is supposed to enable coordination, there are no tools for any meaningful operations, making it severely incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources