@leadbay/mcp 0.23.13 → 0.24.0
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 +15 -0
- package/dist/bin.js +620 -229
- package/dist/http-server.js +606 -225
- package/dist/installer-electron.js +1 -1
- package/dist/installer-gui.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,20 @@
|
|
|
1
1
|
# Changelog — @leadbay/mcp
|
|
2
2
|
|
|
3
|
+
## 0.24.0 — 2026-07-08
|
|
4
|
+
|
|
5
|
+
Enrichment stays active until done, then self-reports — no reprompt (product#3866).
|
|
6
|
+
|
|
7
|
+
- **`leadbay_enrich_titles` / `leadbay_bulk_enrich_status`** — after launching an async enrichment the agent now stays active in the same turn, polls `leadbay_bulk_enrich_status` until the job is done (`all_done`, or a spaced-poll plateau for contacts the backend can't resolve), then reports the resolved emails/phones + refreshed quota on its own. Previously the agent ended its turn on the launch ack and the user had to reprompt to get results.
|
|
8
|
+
- **`leadbay_bulk_enrich_status`** — the notification fast path now returns per-lead contacts on any `include_contacts` read (not only when terminal), so a plateau report has real contact data; the legacy fan-out scopes progress to the requested titles and channels (email → `email`, phone → `phone_number`), so pre-existing enrichments of other roles/channels no longer inflate a run's counts or flip `all_done` early.
|
|
9
|
+
- **Bulk store** — `notification_id` now survives a file-backed reload (it was previously dropped by `validateRecord`, forcing the slower per-lead fallback on every status check in production).
|
|
10
|
+
- **Edge cases** — bounded polling everywhere (no infinite loops on unresolvable contacts), tracker-pending / aged-pending launches route safely (relaunch is server-idempotent), and explicit "don't wait / background" requests are honored.
|
|
11
|
+
|
|
12
|
+
## 0.23.14 — 2026-07-03
|
|
13
|
+
|
|
14
|
+
Registry: publish the hosted remote endpoint so GitHub Copilot / VS Code can offer Leadbay as a one-click remote connector (product#3861).
|
|
15
|
+
|
|
16
|
+
- **`server.json` `remotes`** — the registry entry now advertises the hosted Streamable HTTP endpoint (`https://mcp.leadbay.app/mcp`) alongside the npm package. Landed in code in 0.23.13 but needs this version bump to actually re-publish to the MCP Registry (the registry won't re-publish an already-published version). Auth is standard MCP OAuth (discovered via `.well-known`), so no header/API-key declaration.
|
|
17
|
+
|
|
3
18
|
## 0.23.13 — 2026-07-03
|
|
4
19
|
|
|
5
20
|
Directory-submission schema fix.
|