@koda-sl/baker-cli 0.141.0-dev.253d2418a → 0.141.0-dev.86f91edc8
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/README.md +2 -5
- package/dist/cli.js +588 -291
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2525,12 +2525,11 @@ Permissions enforced server-side:
|
|
|
2525
2525
|
|
|
2526
2526
|
---
|
|
2527
2527
|
|
|
2528
|
-
### `baker mcp
|
|
2528
|
+
### `baker mcp list | add | remove`
|
|
2529
2529
|
|
|
2530
|
-
|
|
2530
|
+
Manage **custom MCP servers** — point the agent at any remote HTTPS MCP endpoint. Registered tools appear as `mcp__<name>__*` on the next chat message.
|
|
2531
2531
|
|
|
2532
2532
|
```bash
|
|
2533
|
-
baker mcp connected
|
|
2534
2533
|
baker mcp list
|
|
2535
2534
|
baker mcp add --name weather --url https://mcp.example.com/mcp
|
|
2536
2535
|
baker mcp add --name acme --url https://acme.dev/mcp --header "Authorization: Bearer sk-…"
|
|
@@ -2617,8 +2616,6 @@ baker schema ads.google.query # Get query command schema
|
|
|
2617
2616
|
baker schema images.search # Get image search schema
|
|
2618
2617
|
```
|
|
2619
2618
|
|
|
2620
|
-
Not every command registers a schema. On `NOT_FOUND` the error carries a structured `fix` pointing at `--help` and the family's agent doc (`__tooling__/docs/tools/baker/<family>.md` in sandboxes). Every top-level family's `--help` also ends with a `Full guide:` line pointing at that doc; `packages/cli/__tests__/doc-coverage.test.ts` fails CI if a mounted command is missing from its family doc.
|
|
2621
|
-
|
|
2622
2619
|
## Creative Canvas
|
|
2623
2620
|
|
|
2624
2621
|
The creative canvas runs declarative JSON pipelines. You author a graph of nodes (text, image, video, audio, composition, control-flow), `baker canvas run` it, and every node's output drops to disk under `canvas/<run_id>/` so you can watch progress and consume the artifacts.
|