@leadbay/mcp 0.37.0 → 0.38.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 +46 -0
- package/dist/bin.js +357 -252
- package/dist/http-server.js +356 -251
- 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,51 @@
|
|
|
1
1
|
# Changelog — @leadbay/mcp
|
|
2
2
|
|
|
3
|
+
## 0.38.1 — 2026-09-12
|
|
4
|
+
|
|
5
|
+
Five fixes merged since 0.38.0 (#216, #219, #220, #221, #225). The backend
|
|
6
|
+
changes #219 and #220 describe (backend#2030, #2031) reached production in
|
|
7
|
+
backend v3.24.0.
|
|
8
|
+
|
|
9
|
+
- **`leadbay_lead_job_status` results fit in one host result** (#221). A
|
|
10
|
+
delivered item carried the backend's whole `QualifiedLead` (~6.6 KB). 23 of
|
|
11
|
+
them made a 158 KB result that Claude Code moved to a file the session could
|
|
12
|
+
not open (SnapLock rehearsal, prod job `24203dfe`). `splitItems` now keeps
|
|
13
|
+
what the tables read, and trims later rows to company, scores and contact.
|
|
14
|
+
The real job went from 152,750 to 32,114 chars.
|
|
15
|
+
- **A pacing 429 is not a credit wall** (#221). The 10-per-hour and 3-running
|
|
16
|
+
lead-job refusals (`rate_limited` / `active_job_cap`) said "Quota exceeded …
|
|
17
|
+
top up", so the agent offered a Stripe link on an unlimited org. On the
|
|
18
|
+
submit endpoints they now say it is a pacing limit, to wait, and to read the
|
|
19
|
+
running jobs. The code stays `QUOTA_EXCEEDED`.
|
|
20
|
+
- **`leadbay_bulk_enrich_status` counts settled reservations** (#216,
|
|
21
|
+
product#4102). It read `email` / `phone_number` off the `source:"paid"`
|
|
22
|
+
record, which never carries them, so every email or phone poll read
|
|
23
|
+
`done: 0`. It now reads `enrichment.done`.
|
|
24
|
+
- **`max_cost` defaults to 100000 on every plan** (#219). `find_new_leads` and
|
|
25
|
+
`qualify_leads` described a plan-tier default (500/2000/5000). The backend
|
|
26
|
+
now keeps what the requested emails and phones cost out of qualification's
|
|
27
|
+
reach, and refuses a cap below it.
|
|
28
|
+
- **Usage is a share of the plan's quota** (#220, #225). Descriptions, prompts
|
|
29
|
+
and runtime hints no longer quote per-lead prices or call reveals "paid" or
|
|
30
|
+
"billed". Consent asks name what will run, with no amount. The
|
|
31
|
+
`leadbay_account_status` quota gauge keeps its dollars, because there the
|
|
32
|
+
user knows it is their plan.
|
|
33
|
+
|
|
34
|
+
## 0.38.0 — 2026-09-10
|
|
35
|
+
|
|
36
|
+
`leadbay_account_status` now returns `mcp_version`, the version of the server
|
|
37
|
+
answering the call, on every call and on both the stdio and hosted servers.
|
|
38
|
+
|
|
39
|
+
Before this, an agent asked "what version of Leadbay are you running" had no
|
|
40
|
+
answer. The version reached the host only in `initialize`'s `serverInfo`, which
|
|
41
|
+
hosts keep out of the model's context, and in
|
|
42
|
+
`update_available.current_version`, which exists only while an update is
|
|
43
|
+
pending and never on hosted (`http-server.ts` wires no update store).
|
|
44
|
+
|
|
45
|
+
The server wrapper sets the field next to `update_available`; the composite's
|
|
46
|
+
`outputSchema` declares it, and the description gains a routing trigger and one
|
|
47
|
+
sentence telling the agent to answer version questions with it.
|
|
48
|
+
|
|
3
49
|
## 0.37.0 — 2026-09-08
|
|
4
50
|
|
|
5
51
|
Expose the backend MCP-first delivery endpoints (`POST /1.6/mcp/search`,
|