@leadbay/mcp 0.36.0 → 0.38.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 +35 -0
- package/dist/bin.js +2842 -244
- package/dist/http-server.js +2690 -132
- 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,40 @@
|
|
|
1
1
|
# Changelog — @leadbay/mcp
|
|
2
2
|
|
|
3
|
+
## 0.38.0 — 2026-09-10
|
|
4
|
+
|
|
5
|
+
`leadbay_account_status` now returns `mcp_version`, the version of the server
|
|
6
|
+
answering the call, on every call and on both the stdio and hosted servers.
|
|
7
|
+
|
|
8
|
+
Before this, an agent asked "what version of Leadbay are you running" had no
|
|
9
|
+
answer. The version reached the host only in `initialize`'s `serverInfo`, which
|
|
10
|
+
hosts keep out of the model's context, and in
|
|
11
|
+
`update_available.current_version`, which exists only while an update is
|
|
12
|
+
pending and never on hosted (`http-server.ts` wires no update store).
|
|
13
|
+
|
|
14
|
+
The server wrapper sets the field next to `update_available`; the composite's
|
|
15
|
+
`outputSchema` declares it, and the description gains a routing trigger and one
|
|
16
|
+
sentence telling the agent to answer version questions with it.
|
|
17
|
+
|
|
18
|
+
## 0.37.0 — 2026-09-08
|
|
19
|
+
|
|
20
|
+
Expose the backend MCP-first delivery endpoints (`POST /1.6/mcp/search`,
|
|
21
|
+
`POST /1.6/mcp/qualify`, `GET /1.6/mcp/jobs/{id}`) as three composites —
|
|
22
|
+
`leadbay_find_new_leads`, `leadbay_qualify_leads`, `leadbay_lead_job_status` —
|
|
23
|
+
plus the `leadbay_new_leads` guided prompt. One ask → net-new qualified
|
|
24
|
+
contactable leads, replacing the pull→select→web_fetch→poll→enrich chain.
|
|
25
|
+
|
|
26
|
+
Free by default (`qualify: false`, no `channels`). Any paid call is withheld
|
|
27
|
+
until `confirm: true` and returns a real backend quote instead; `confirm: false`
|
|
28
|
+
vetoes with no round-trip. A derived `request_id` makes a retried paid batch
|
|
29
|
+
return the same job rather than double-charge, and `max_cost` stops the job with
|
|
30
|
+
`stop_reason: "max_cost"`.
|
|
31
|
+
|
|
32
|
+
The `LEADBAY_MCP_LEAD_DELIVERY` rollout flag introduced with these tools is
|
|
33
|
+
retired: the routes shipped to production in backend v3.22.0 (2026-08-22) and
|
|
34
|
+
were verified live on `api-us` and `api-fr`. The `leadbay_new_leads` prompt is
|
|
35
|
+
still hidden on a read-only server (`LEADBAY_MCP_WRITE=0`), since every phase of
|
|
36
|
+
it calls a write-tier tool.
|
|
37
|
+
|
|
3
38
|
## 0.36.0 — 2026-09-08
|
|
4
39
|
|
|
5
40
|
The OpenAI submission form flags every tool without an `outputSchema`
|