@leadbay/mcp 0.6.0 → 0.6.2

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,6 +1,16 @@
1
1
  # Changelog — @leadbay/mcp
2
2
 
3
- ## 0.6.0 — UNRELEASED
3
+ ## 0.6.2 — UNRELEASED
4
+
5
+ **MCPB install fix**: desktop extension bundles now use the current `manifest_version` field and remove unsupported manifest keys (`user_config.*.enum` and an internal note field) so Claude Desktop can preview and install the MCPB.
6
+
7
+ ## 0.6.1 — 2026-05-10
8
+
9
+ **Distribution**: listed in the official MCP Registry as `io.github.leadbay/leadbay-mcp` (auto-published from CI via GitHub OIDC); installable as a Claude Code plugin via `/plugin marketplace add leadbay/leadclaw` then `/plugin install leadbay@leadbay-leadclaw`; submission packets prepared for the Claude.ai connector directory and Anthropic's curated MCPB extension directory.
10
+
11
+ **Registry verification**: adds `mcpName` to the npm package metadata so the MCP Registry can verify ownership of `io.github.leadbay/leadbay-mcp` against the published `@leadbay/mcp` package.
12
+
13
+ ## 0.6.0 — 2026-05-08
4
14
 
5
15
  Massive spec-coverage upgrade. Each tool declares **annotations** (`readOnlyHint` / `destructiveHint` / `idempotentHint` / `openWorldHint`); 17 composites + 12 highest-leverage granulars declare typed `outputSchema` + emit `structuredContent`. New surfaces: `prompts/*` (5 canned slash-commands), `resources/*` (`lead://`, `lens://`, `org://taste-profile`), `notifications/progress` (per-lead streaming on every long-running composite), `notifications/cancelled` → `ToolContext.signal` (bulk-store entries marked `cancelled` so subsequent status polls return `BULK_CANCELLED`), `elicitation/create` (refine_prompt clarification + report_outreach user_confirmed anti-poisoning).
6
16
 
package/README.md CHANGED
@@ -1,5 +1,7 @@
1
1
  # @leadbay/mcp — Leadbay MCP server
2
2
 
3
+ [![MCP Registry](https://img.shields.io/badge/MCP%20Registry-io.github.leadbay%2Fleadbay--mcp-blue)](https://registry.modelcontextprotocol.io/v0/servers/io.github.leadbay/leadbay-mcp)
4
+
3
5
  <!--
4
6
  LLM HINT — if you're an AI agent reading this README to install the server:
5
7
  - Use ONLY the commands shown verbatim in §1. Do not invent variants.
@@ -15,7 +17,7 @@ LLM HINT — if you're an AI agent reading this README to install the server:
15
17
 
16
18
  A Model Context Protocol server that lets Claude Desktop, Cursor, Claude Code, and any other MCP-compatible agent find, research, and prepare outreach on B2B prospects using your Leadbay account.
17
19
 
18
- > **0.6.0 — what's new** (UNRELEASED): a comprehensive MCP-spec coverage upgrade. Every tool now declares **annotations** (`readOnlyHint`/`destructiveHint`/`idempotentHint`/`openWorldHint`) so capable clients pick the right confirmation UX. The 5 highest-traffic composites ship **`outputSchema` + `structuredContent`** for typed agent consumption. New surfaces: **`prompts/*`** (5 canned slash-commands), **`resources/*`** (`lead://`, `lens://`, `org://taste-profile`), **`notifications/progress`** (per-lead streaming during `bulk_qualify_leads`), **`notifications/cancelled` → `ToolContext.signal`** (client cancels actually stop polling), **`elicitation/create`** (server can ask the user directly). Schema strictness: every `inputSchema` now declares `additionalProperties: false`. `research_lead.qualification[]` ships `boost_score` (canonical) + `score_scale: "-10|0|10|20"` + a deprecated `score_0_to_10` alias. Pagination payloads include `has_more` + `next_page`. `research_lead` includes a `truncated` + `truncation_hint` budget guard. **Behavior callout**: extra unknown fields in tool inputs are now rejected. See [MIGRATION.md](./MIGRATION.md).
20
+ > **0.6.x — what's new**: a comprehensive MCP-spec coverage upgrade. Every tool now declares **annotations** (`readOnlyHint`/`destructiveHint`/`idempotentHint`/`openWorldHint`) so capable clients pick the right confirmation UX. The 5 highest-traffic composites ship **`outputSchema` + `structuredContent`** for typed agent consumption. New surfaces: **`prompts/*`** (5 canned slash-commands), **`resources/*`** (`lead://`, `lens://`, `org://taste-profile`), **`notifications/progress`** (per-lead streaming during `bulk_qualify_leads`), **`notifications/cancelled` → `ToolContext.signal`** (client cancels actually stop polling), **`elicitation/create`** (server can ask the user directly). Schema strictness: every `inputSchema` now declares `additionalProperties: false`. `research_lead.qualification[]` ships `boost_score` (canonical) + `score_scale: "-10|0|10|20"` + a deprecated `score_0_to_10` alias. Pagination payloads include `has_more` + `next_page`. `research_lead` includes a `truncated` + `truncation_hint` budget guard. **Behavior callout**: extra unknown fields in tool inputs are now rejected. See [MIGRATION.md](./MIGRATION.md).
19
21
 
20
22
  > **0.3.0 behavior change** — composite write tools (`refine_prompt`, `report_outreach`, `adjust_audience`, `bulk_qualify_leads`, `enrich_titles`, `answer_clarification`, `import_leads`) are **ON by default**. Set `LEADBAY_MCP_WRITE=0` (or `--no-write` on `install`) to restore the previous read-only behavior. `leadbay-mcp install` now also registers Claude Code at `--scope user` so Leadbay is visible from any project. See [MIGRATION.md](./MIGRATION.md).
21
23
 
@@ -41,6 +43,15 @@ The token is **session-scoped** (full account access, password-equivalent). Trea
41
43
 
42
44
  **Don't have a Leadbay account?** [Register here](https://wow.leadbay.ai/?register=true).
43
45
 
46
+ ### Install via the Claude Code plugin marketplace
47
+
48
+ ```text
49
+ /plugin marketplace add leadbay/leadclaw
50
+ /plugin install leadbay@leadbay-leadclaw
51
+ ```
52
+
53
+ Claude Code prompts for your token and region through the plugin's `userConfig`. This is equivalent to the npm/CLI install above; users who already ran `leadbay-mcp login` can reuse that token.
54
+
44
55
  ### Claude Desktop 2026 (DXT)
45
56
 
46
57
  Claude Desktop 2026 ships the DXT (Desktop Extension) system — the legacy `claude_desktop_config.json` is UI-prefs-only there and gets overwritten by the app. If you're on 2026, **install the `.dxt` bundle** from [Releases](https://github.com/leadbay/leadclaw/releases/latest) (drag-drop into Settings → Extensions). `leadbay-mcp install` detects this and skips the legacy write automatically.
package/dist/bin.js CHANGED
@@ -387,7 +387,7 @@ function buildServer(client, opts = {}) {
387
387
  }
388
388
  const exposedNames = new Set(toolByName.keys());
389
389
  const server = new Server(
390
- { name: "leadbay", version: "0.6.0" },
390
+ { name: "leadbay", version: "0.6.2" },
391
391
  {
392
392
  capabilities: {
393
393
  tools: {},
@@ -587,7 +587,7 @@ function buildServer(client, opts = {}) {
587
587
 
588
588
  // src/bin.ts
589
589
  import { createRequire } from "module";
590
- var VERSION = "0.6.0";
590
+ var VERSION = "0.6.2";
591
591
  var HELP = `
592
592
  leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
593
593
 
package/package.json CHANGED
@@ -1,6 +1,7 @@
1
1
  {
2
2
  "name": "@leadbay/mcp",
3
- "version": "0.6.0",
3
+ "version": "0.6.2",
4
+ "mcpName": "io.github.leadbay/leadbay-mcp",
4
5
  "description": "Model Context Protocol (MCP) server for Leadbay — AI lead discovery, qualification, and enrichment for Claude Desktop, Cursor, and Claude Code.",
5
6
  "type": "module",
6
7
  "bin": {