Cursor plugin

Overview

The Wolbarg Cursor plugin (@wolbarg/cursor) turns Wolbarg’s coordination plane into something Cursor agents use natively:

• MCP tools — briefing, claims, findings, handoffs, readiness
• Skill — when and how agents should coordinate
• Rules — always-on short contract
• Hooks — session briefing + write-path claim checks

This is not another coding agent and not an orchestrator. Cursor remains the runtime. Wolbarg provides shared memory + coordination so multiple agents in the same workspace stop colliding and stop forgetting what siblings already learned.

Status: @wolbarg/cursor@0.2.0 — production-ready after wolbarg init (and, for hard guarantees, fail-closed protected paths). Verify with MCP tool production_readiness (ready: true).

Install

One-click (recommended)

These buttons open Cursor’s install flow. Setup Cursor opens this page’s install section only when you need the full guide from elsewhere — here, use Add to Cursor to install.

If the deeplink does not open Cursor (browser blocked the protocol), use the Marketplace button or Option C below.

Hard requirement: wolbarg init

After installing the plugin / MCP server, initialize the workspace:

npx wolbarg init

That writes .wolbarg/config.json. Without it:

• MCP starts in setup mode (tools return WOLBARG_NOT_INITIALIZED instead of crashing)
• Hooks deny / warn until init exists
• CoordinationPlane throws under default options

After init, reload MCP or reopen the agent chat.

Option A — project MCP (absolute paths on Windows)

Create or edit .cursor/mcp.json in the workspace:

{
  "mcpServers": {
    "wolbarg-cursor-mcp": {
      "command": "npx",
      "args": ["-y", "@wolbarg/cursor"],
      "env": {
        "WOLBARG_WORKSPACE_ROOT": "C:/absolute/path/to/workspace"
      }
    }
  }
}

For a local monorepo build:

{
  "mcpServers": {
    "wolbarg-cursor-mcp": {
      "command": "node",
      "args": ["C:/absolute/path/to/plugins/cursor/dist/mcp-server.js"],
      "env": {
        "WOLBARG_WORKSPACE_ROOT": "C:/absolute/path/to/workspace"
      }
    }
  }
}

Option B — Cursor plugin (local symlink)

# macOS / Linux
mkdir -p ~/.cursor/plugins/local
ln -s "$(pwd)/plugins/cursor" ~/.cursor/plugins/local/wolbarg-cursor-mcp

Option C — npm bin

npx -y @wolbarg/cursor

Same entrypoint the Add to Cursor deeplink configures.

Agent workflow

Use this loop whenever multiple Cursor agents (or parallel chats) touch the same repo:

1. workspace_briefing — short queries; pass wait_ms when siblings may still be writing
2. claim_scope — lease paths before contested edits
3. record_finding — facts / decisions / dead ends (+ tags)
4. pulse_update / heartbeat_claim — keep leases alive while working
5. release_claim + create_handoff — free paths and pass context
6. compliance_report / production_readiness — ops gates

Example prompts for agents

Ask the agent (with Wolbarg MCP enabled):

• “Call workspace_briefing for auth and payments, then summarize open claims.”
• “Claim src/billing/**, implement the invoice fix, then release and create a handoff.”
• “Record a dead_end finding: Stripe webhook retries conflict with our idempotency key.”
• “Run production_readiness and list blockers.”

MCP tools

Production checklist

Recommended production policy

{
  "enforcement": "fail_closed_protected_paths",
  "protectedGlobs": ["src/auth/**", "src/payments/**", "src/billing/**"],
  "defaultClaimTtlSeconds": 1800,
  "allowClaimBreakBy": "human",
  "pulseTtlSeconds": 900
}

Default remains advisory for gentle onboarding; production deployments should switch to fail-closed on protected globs.

Library API

import { CoordinationPlane } from "@wolbarg/cursor";

const plane = new CoordinationPlane({ rootPath: process.cwd() });
const gate = plane.productionReadiness();
if (!gate.ready) throw new Error(gate.blockers.join("\n"));
plane.close();

Design notes

• Init is mandatory for full plane operation.
• Git remains code source of truth — the coordination DB holds leases, findings, and compliance only.
• Claims use TTL + heartbeat — crashed agents expire.
• Findings use local FTS; core Wolbarg semantic memory uses your project embedding config separately.
• Requires Node.js ≥ 22.5.

Troubleshooting

Related

• Connectors overview
• Shared memory guide
• Getting started
• Plugin source: plugins/cursor