@leadbay/mcp 0.10.0 → 0.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Changelog — @leadbay/mcp
2
2
 
3
+ ## 0.10.1 — 2026-05-20
4
+
5
+ Documentation + version-pin sweep paired with hardening the release pipeline. No functional changes to the published binary.
6
+
7
+ - **Pin bumps**: every `npx -y @leadbay/mcp@<old>` reference in `bin.ts` (install command output, error hints, doctor instructions, generated client configs), `README.md`, `server.json` (MCP Registry manifest), `packages/dxt/manifest.template.json`, and `.claude-plugin/plugins/leadbay/.claude-plugin/plugin.json` is now `@0.10`. New installs land on the latest minor.
8
+ - **Release pipeline migrated to npm Trusted Publishers OIDC** (`.github/workflows/release.yml`): npm revoked Classic tokens on Dec 9 2025 and Granular tokens with the "Bypass 2FA" flag still hit known publish-rejection bugs ([npm/cli#9268](https://github.com/npm/cli/issues/9268)). The publish step now uses OIDC via the [Trusted Publishers binding](https://docs.npmjs.com/trusted-publishers) configured per-package on npmjs.com. Runtime bumped to Node 24 in publish jobs for the bundled npm ≥ 11.5 that speaks the OIDC handshake (Node 22's npm 10 can't, and self-upgrade via `npm install -g npm@latest` consistently breaks on the runner image).
9
+ - **Auto-release** (existing `.github/workflows/auto-tag.yml` — unchanged in this release, documented here): merges to `main` that bump `packages/mcp/package.json#version` automatically push `mcp-v<ver>` and dispatch `release.yml` on the tag, which publishes to npm + MCP Registry + uploads the .dxt to a GitHub Release. No manual tagging needed.
10
+
3
11
  ## 0.10.0 — 2026-05-19
4
12
 
5
13
  First stable cut of the 0.10 line. Consolidates everything since 0.9.1: host-native widget rendering, structured routing schema, the top-up flow, like/dislike write tools, the `research_lead` split, and PostHog + Sentry telemetry. See dev-iteration commits for granular per-PR history; this is the npm-shipped consolidation.
package/README.md CHANGED
@@ -24,7 +24,7 @@ A Model Context Protocol server that lets Claude Desktop, Cursor, Claude Code, a
24
24
  ## 1. Install (one command)
25
25
 
26
26
  ```bash
27
- npx -y @leadbay/mcp@0.6 install --email you@yourcompany.com --region us
27
+ npx -y @leadbay/mcp@0.10 install --email you@yourcompany.com --region us
28
28
  # (you'll be prompted for your password — it's not echoed)
29
29
  ```
30
30
 
@@ -67,14 +67,14 @@ Claude Desktop 2026 ships the DXT (Desktop Extension) system — the legacy `cla
67
67
 
68
68
  If you installed Node from the official [nodejs.org](https://nodejs.org) `.pkg`, `/usr/local/lib/node_modules` is root-owned. Any of these works:
69
69
 
70
- - **Use `npx` (recommended, no global install):** all examples above use `npx -y @leadbay/mcp@0.6 ...` — no global install needed.
70
+ - **Use `npx` (recommended, no global install):** all examples above use `npx -y @leadbay/mcp@0.10 ...` — no global install needed.
71
71
  - **`sudo npm install -g @leadbay/mcp`** (enter your macOS password).
72
72
  - **Use a Node version manager** — [nvm](https://github.com/nvm-sh/nvm), [volta](https://volta.sh), [fnm](https://github.com/Schniz/fnm). They install Node under your home directory, so `npm install -g` works without sudo.
73
73
 
74
74
  ### If you'd rather mint a token without auto-install
75
75
 
76
76
  ```bash
77
- npx -y @leadbay/mcp@0.6 login \
77
+ npx -y @leadbay/mcp@0.10 login \
78
78
  --email you@yourcompany.com \
79
79
  --region us
80
80
  ```
@@ -92,7 +92,7 @@ Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) o
92
92
  "mcpServers": {
93
93
  "leadbay": {
94
94
  "command": "npx",
95
- "args": ["-y", "@leadbay/mcp@0.6"],
95
+ "args": ["-y", "@leadbay/mcp@0.10"],
96
96
  "env": {
97
97
  "LEADBAY_TOKEN": "<paste-token-from-step-1>",
98
98
  "LEADBAY_REGION": "us"
@@ -113,7 +113,7 @@ In Cursor settings, add the MCP server:
113
113
  "mcp.servers": {
114
114
  "leadbay": {
115
115
  "command": "npx",
116
- "args": ["-y", "@leadbay/mcp@0.6"],
116
+ "args": ["-y", "@leadbay/mcp@0.10"],
117
117
  "env": { "LEADBAY_TOKEN": "<paste-token>", "LEADBAY_REGION": "us" }
118
118
  }
119
119
  }
@@ -126,7 +126,7 @@ In Cursor settings, add the MCP server:
126
126
  claude mcp add leadbay --scope user \
127
127
  --env LEADBAY_TOKEN=<paste-token> \
128
128
  --env LEADBAY_REGION=us \
129
- -- npx -y @leadbay/mcp@0.6
129
+ -- npx -y @leadbay/mcp@0.10
130
130
  ```
131
131
 
132
132
  > **`--scope user`** registers Leadbay globally for your account (visible from any project). Without it, `claude mcp add` defaults to project-local scope and the server only appears in conversations opened from the directory where you ran the command.
@@ -138,7 +138,7 @@ claude mcp add leadbay --scope user \
138
138
  Before starting Claude, run:
139
139
 
140
140
  ```bash
141
- LEADBAY_TOKEN=<paste-token> npx -y @leadbay/mcp@0.6 doctor
141
+ LEADBAY_TOKEN=<paste-token> npx -y @leadbay/mcp@0.10 doctor
142
142
  ```
143
143
 
144
144
  Expected output:
@@ -366,14 +366,14 @@ The user's literal text replaces `verification.ref` in the outreach record, and
366
366
  | `No enrichment credits remaining` | Out of quota | Contact Leadbay support to extend quota |
367
367
  | Claude Desktop "loading forever" on first use | `npx` cold-start fetching the package | First run takes ~10s. Prefer `npm install -g @leadbay/mcp` for faster startup. |
368
368
  | Claude Desktop doesn't show Leadbay tools | Server crashed at startup | Check `~/Library/Logs/Claude/mcp*.log` (macOS) or `%APPDATA%\Claude\logs\mcp*.log` (Windows). |
369
- | Claude Code can't find Leadbay in a new conversation | MCP server installed at project scope (default before 0.3.0) | Re-run with `--scope user`: `claude mcp remove leadbay && claude mcp add leadbay --scope user --env LEADBAY_TOKEN=… --env LEADBAY_REGION=us -- npx -y @leadbay/mcp@0.6` |
369
+ | Claude Code can't find Leadbay in a new conversation | MCP server installed at project scope (default before 0.3.0) | Re-run with `--scope user`: `claude mcp remove leadbay && claude mcp add leadbay --scope user --env LEADBAY_TOKEN=… --env LEADBAY_REGION=us -- npx -y @leadbay/mcp@0.10` |
370
370
  | Agent reports "tool not found" for `refine_prompt` / `adjust_audience` etc. | Pre-0.3.0 install with `LEADBAY_MCP_WRITE` unset (writes were off) | Either re-run `npx @leadbay/mcp install` or remove `LEADBAY_MCP_WRITE=0` from your client config (writes are on by default in 0.3.0+) |
371
371
 
372
372
  ## 5. Upgrade & rotation
373
373
 
374
- **Upgrade**: change the pinned minor in your config, e.g. `"@leadbay/mcp@0.2"` → `"@leadbay/mcp@0.6"`, then restart the client. **0.3.0 enables composite write tools by default** — see [MIGRATION.md](./MIGRATION.md). See also the [changelog](https://github.com/leadbay/leadclaw/releases).
374
+ **Upgrade**: change the pinned minor in your config, e.g. `"@leadbay/mcp@0.2"` → `"@leadbay/mcp@0.10"`, then restart the client. **0.3.0 enables composite write tools by default** — see [MIGRATION.md](./MIGRATION.md). See also the [changelog](https://github.com/leadbay/leadclaw/releases).
375
375
 
376
- **Rotate token**: re-run `npx -y @leadbay/mcp@0.6 install --email you@yourcompany.com --region us` (or `login`) — the new session token replaces the old one in your MCP client config, and logging in again invalidates the prior session on most session backends.
376
+ **Rotate token**: re-run `npx -y @leadbay/mcp@0.10 install --email you@yourcompany.com --region us` (or `login`) — the new session token replaces the old one in your MCP client config, and logging in again invalidates the prior session on most session backends.
377
377
 
378
378
  ## 6. Advanced
379
379
 
package/dist/bin.js CHANGED
@@ -1661,7 +1661,7 @@ function buildServer(client, opts = {}) {
1661
1661
 
1662
1662
  // src/bin.ts
1663
1663
  import { createRequire } from "module";
1664
- var VERSION = "0.10.0";
1664
+ var VERSION = "0.10.1";
1665
1665
  var HELP = `
1666
1666
  leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
1667
1667
 
@@ -1710,7 +1710,7 @@ EXAMPLE Claude Desktop config (~/Library/Application Support/Claude/claude_deskt
1710
1710
  "mcpServers": {
1711
1711
  "leadbay": {
1712
1712
  "command": "npx",
1713
- "args": ["-y", "@leadbay/mcp@0.3"],
1713
+ "args": ["-y", "@leadbay/mcp@0.10"],
1714
1714
  "env": {
1715
1715
  "LEADBAY_TOKEN": "lb_...",
1716
1716
  "LEADBAY_REGION": "us",
@@ -1977,7 +1977,7 @@ async function runLogin(args) {
1977
1977
  mcpServers: {
1978
1978
  leadbay: {
1979
1979
  command: "npx",
1980
- args: ["-y", "@leadbay/mcp@0.3"],
1980
+ args: ["-y", "@leadbay/mcp@0.10"],
1981
1981
  env: {
1982
1982
  LEADBAY_TOKEN: result.token,
1983
1983
  LEADBAY_REGION: result.region
@@ -2017,7 +2017,7 @@ Or for Claude Code (token included \u2014 same warning applies):
2017
2017
  claude mcp add leadbay --scope user \\
2018
2018
  --env LEADBAY_TOKEN=${result.token} \\
2019
2019
  --env LEADBAY_REGION=${result.region} \\
2020
- -- npx -y @leadbay/mcp@0.3
2020
+ -- npx -y @leadbay/mcp@0.10
2021
2021
 
2022
2022
  Restart your MCP client to pick up the new server.
2023
2023
  `
@@ -2123,7 +2123,7 @@ For Claude Code, run:
2123
2123
  claude mcp add leadbay --scope user \\
2124
2124
  --env LEADBAY_TOKEN=$(jq -r .mcpServers.leadbay.env.LEADBAY_TOKEN ${quotedPath}) \\
2125
2125
  --env LEADBAY_REGION=${result.region} \\
2126
- -- npx -y @leadbay/mcp@0.3
2126
+ -- npx -y @leadbay/mcp@0.10
2127
2127
  `
2128
2128
  );
2129
2129
  }
@@ -2303,7 +2303,7 @@ function buildClaudeCodeAddArgs(token, region, includeWrite, telemetryEnabled) {
2303
2303
  `LEADBAY_TELEMETRY_ENABLED=${telemetryEnabled ? "true" : "false"}`
2304
2304
  ];
2305
2305
  if (!includeWrite) args.push("--env", `LEADBAY_MCP_WRITE=0`);
2306
- args.push("--", "npx", "-y", "@leadbay/mcp@0.3");
2306
+ args.push("--", "npx", "-y", "@leadbay/mcp@0.10");
2307
2307
  return args;
2308
2308
  }
2309
2309
  async function installInClaudeCode(token, region, includeWrite, telemetryEnabled) {
@@ -2353,7 +2353,7 @@ async function installInJsonConfig(configPath, token, region, includeWrite, tele
2353
2353
  if (!includeWrite) env.LEADBAY_MCP_WRITE = "0";
2354
2354
  parsed.mcpServers.leadbay = {
2355
2355
  command: "npx",
2356
- args: ["-y", "@leadbay/mcp@0.3"],
2356
+ args: ["-y", "@leadbay/mcp@0.10"],
2357
2357
  env
2358
2358
  };
2359
2359
  const tmp = configPath + ".tmp";
@@ -2530,7 +2530,7 @@ leadbay-mcp install \u2014 detected MCP clients on this machine:
2530
2530
  process.stderr.write(
2531
2531
  `
2532
2532
  The token was written into client config files but never printed to your terminal.
2533
- Verify with: LEADBAY_TOKEN=$(...) npx -y @leadbay/mcp@0.3 doctor
2533
+ Verify with: LEADBAY_TOKEN=$(...) npx -y @leadbay/mcp@0.10 doctor
2534
2534
  Restart your MCP client(s) to pick up the new server.
2535
2535
  If you ever leak the token, run \`leadbay-mcp login --email <you> --region <us|fr>\` to mint a fresh one (which invalidates the prior session).
2536
2536
  `
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@leadbay/mcp",
3
- "version": "0.10.0",
3
+ "version": "0.10.1",
4
4
  "mcpName": "io.github.leadbay/leadbay-mcp",
5
5
  "description": "Model Context Protocol (MCP) server for Leadbay — AI lead discovery, qualification, and enrichment for Claude Desktop, Cursor, and Claude Code.",
6
6
  "type": "module",