Skillsoft Service Bootstrap (MCP demo)

npm (unscoped, personal publish): skillsoft-service-bootstrap · MCP / log id: skillsoft-service-bootstrap · CLI: skillsoft-service-bootstrap · sources: mcp/repo-dev-tools/ in this monorepo.

Skillsoft is only a name here (demo / internal-style naming). There is no scoped @…/… package: publish to public npm (or any registry) from your personal account after setting "private": false and fixing "repository".

Two ways to wire Cursor / VS Code MCP:

1. npm package — install skillsoft-service-bootstrap, then point MCP at node + server.mjs or npx -y skillsoft-service-bootstrap (see below).
2. VS Code extension (“Skillsoft Service Bootstrap”) in extension/ — copies MCP JSON snippets (local server.mjs, workspace node_modules, or npx). Build a VSIX with npm run package-extension from mcp/repo-dev-tools (network for npx @vscode/vsce). Set publisher in extension/package.json before marketplace publish.

A. Publish skillsoft-service-bootstrap to npm (personal account)

From mcp/repo-dev-tools/:

1. Set "repository"."url" in package.json to your real Git URL (optional but recommended for npm).
2. Set "private": false when you are ready to publish.
3. npm login (your user) → npm publish.

Consumer project:

npm install -D skillsoft-service-bootstrap

Cursor mcp.json (workspace or user):

{
  "mcpServers": {
    "skillsoft-service-bootstrap": {
      "command": "node",
      "args": ["${workspaceFolder}/node_modules/skillsoft-service-bootstrap/server.mjs"],
      "cwd": "${workspaceFolder}"
    }
  }
}

Or npx (no install):

{
  "mcpServers": {
    "skillsoft-service-bootstrap": {
      "command": "npx",
      "args": ["-y", "skillsoft-service-bootstrap"],
      "cwd": "${workspaceFolder}"
    }
  }
}

B. Monorepo / clone (no publish)

1. Run npm install inside mcp/repo-dev-tools/ once per clone.
2. Point MCP at the absolute path to server.mjs, "cwd": "${workspaceFolder}" (see goals-streaks/mcp/user-mcp-global.example.json).

Each app keeps mcp/repo-profile.json (or mcp/bringup-mcp/repo-profile.json): skillsoft-service-bootstrap loads the former if present, otherwise the latter.

C. VS Code / Cursor extension (extension/)

1. Open mcp/repo-dev-tools/extension in VS Code (or Cursor).
2. Run → Start Debugging (F5) to try the extension in a new window.
3. Command Palette:
   • Skillsoft Service Bootstrap: MCP (bundled server) — when server.mjs is one level above extension/ (this repo).
   • Skillsoft Service Bootstrap: MCP (node_modules) — after npm install skillsoft-service-bootstrap in the workspace.
   • Skillsoft Service Bootstrap: MCP (npx) — after the npm package is published.

From mcp/repo-dev-tools: npm run package-extension writes a VSIX under extension/ (for example skillsoft-service-bootstrap-0.1.0.vsix, matching extension/package.json version). Set publisher in extension/package.json first.

The extension does not replace the MCP server; it only helps paste MCP config. You can use MCP only, extension only as a helper, or both.

After install

• Each application repo needs mcp/repo-profile.json or mcp/bringup-mcp/repo-profile.json (copy from a repo-profile.example.json or ship beside bringup-mcp).

Layout (1.11+)

• server.mjs — entry: MCP version from package.json, registers tools, CLI flags.
• register-tools.mjs — registerTool handlers with stderr-safe errors.
• lib/*.mjs — profile, infra, scans, markdown, orchestration, optional apply_repo_text_patch.
• extension/ — optional VS Code companion (clipboard MCP snippets).

Version

McpServer version is read from package.json at startup; bump version when you publish.