@leadbay/mcp 0.36.0 → 0.37.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 CHANGED
@@ -1,5 +1,25 @@
1
1
  # Changelog — @leadbay/mcp
2
2
 
3
+ ## 0.37.0 — 2026-09-08
4
+
5
+ Expose the backend MCP-first delivery endpoints (`POST /1.6/mcp/search`,
6
+ `POST /1.6/mcp/qualify`, `GET /1.6/mcp/jobs/{id}`) as three composites —
7
+ `leadbay_find_new_leads`, `leadbay_qualify_leads`, `leadbay_lead_job_status` —
8
+ plus the `leadbay_new_leads` guided prompt. One ask → net-new qualified
9
+ contactable leads, replacing the pull→select→web_fetch→poll→enrich chain.
10
+
11
+ Free by default (`qualify: false`, no `channels`). Any paid call is withheld
12
+ until `confirm: true` and returns a real backend quote instead; `confirm: false`
13
+ vetoes with no round-trip. A derived `request_id` makes a retried paid batch
14
+ return the same job rather than double-charge, and `max_cost` stops the job with
15
+ `stop_reason: "max_cost"`.
16
+
17
+ The `LEADBAY_MCP_LEAD_DELIVERY` rollout flag introduced with these tools is
18
+ retired: the routes shipped to production in backend v3.22.0 (2026-08-22) and
19
+ were verified live on `api-us` and `api-fr`. The `leadbay_new_leads` prompt is
20
+ still hidden on a read-only server (`LEADBAY_MCP_WRITE=0`), since every phase of
21
+ it calls a write-tier tool.
22
+
3
23
  ## 0.36.0 — 2026-09-08
4
24
 
5
25
  The OpenAI submission form flags every tool without an `outputSchema`