@leadbay/mcp 0.41.1 → 0.43.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 +33 -0
- package/dist/bin.js +191 -30
- package/dist/http-server.js +172 -28
- 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,38 @@
|
|
|
1
1
|
# Changelog — @leadbay/mcp
|
|
2
2
|
|
|
3
|
+
## 0.43.0 — 2026-09-30 — a misnamed argument is read or named, never dropped
|
|
4
|
+
|
|
5
|
+
- **`lead_id` and `leadId` both work.** Leadbay tools spell the lead id
|
|
6
|
+
differently: researching a lead and adding a note take `leadId`, setting a
|
|
7
|
+
CRM status takes `lead_ids`. An assistant that used the other spelling was
|
|
8
|
+
told the id was missing, and a scheduled run lost a night's notes and
|
|
9
|
+
statuses this way. An argument that differs only by capitals or underscores
|
|
10
|
+
is now read as the one the tool expects, and setting a status also takes a
|
|
11
|
+
single lead id.
|
|
12
|
+
- **Any other unknown argument is named.** It used to be dropped silently. It
|
|
13
|
+
now comes back as an error that names it, suggests the argument it probably
|
|
14
|
+
meant, and lists the ones the tool takes. A call rejected this way writes
|
|
15
|
+
nothing.
|
|
16
|
+
- **Team prospecting setup names the right arguments.** It told the assistant
|
|
17
|
+
to pass `user_prompt` to two tools that take `prompt` and `base`.
|
|
18
|
+
|
|
19
|
+
## 0.42.0 — 2026-09-28 — every rep gets the same boards
|
|
20
|
+
|
|
21
|
+
- **The route planner and the lead triage board are now finished pages.**
|
|
22
|
+
Asking for either, or picking it from the suggested next steps, gives every
|
|
23
|
+
rep exactly the same board, in the same layout and colours, rather than a
|
|
24
|
+
page the assistant rebuilds each time. Each page loads its own leads when it
|
|
25
|
+
opens.
|
|
26
|
+
- **The route planner shows your country.** A US workspace gets a map of the
|
|
27
|
+
United States, the lower 48 in view, instead of France. French workspaces
|
|
28
|
+
keep the map of France, départements and islands included.
|
|
29
|
+
- **The map opens on the whole country, filling the panel.** It used to open
|
|
30
|
+
zoomed out, with the country small in a wide margin. It now fits the
|
|
31
|
+
country to the space, and keeps fitting it while the page settles, until you
|
|
32
|
+
move the map yourself.
|
|
33
|
+
- **Planning a trip to a city opens the planner on that city.** After "I'm in
|
|
34
|
+
Lyon on Thursday", the planner opens with Lyon already filtered.
|
|
35
|
+
|
|
3
36
|
## 0.41.1 — 2026-09-26 — triage boards stop drawing a second outcome control
|
|
4
37
|
|
|
5
38
|
- **Triage boards are built with the same outreach controls as the web app.**
|