From d5e734685019bb2dd6f461f5ef28232416c84458 Mon Sep 17 00:00:00 2001 From: max Date: Mon, 14 Sep 2026 18:36:02 +0200 Subject: [PATCH 1/2] Document saving editable KCL in the MCP walkthrough --- content/pages/docs/developer-tools/mcp/index.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/pages/docs/developer-tools/mcp/index.mdx b/content/pages/docs/developer-tools/mcp/index.mdx index f5fec341..1806e485 100644 --- a/content/pages/docs/developer-tools/mcp/index.mdx +++ b/content/pages/docs/developer-tools/mcp/index.mdx @@ -95,9 +95,9 @@ Here is a simple version using Codex or Claude Code: 1. Open your MCP-compatible AI client. 2. Connect Zoo MCP with `uvx zoo-mcp` and your `ZOO_API_TOKEN`. 3. Ask for something concrete, for example: "Create a simple mounting bracket with two bolt holes." -4. Let the assistant use Zoo MCP to generate the result. -5. Open the files or project output in Zoo Design Studio. -6. Inspect the geometry, review the files, and keep editing from there. +4. Have the assistant save `main.kcl` and any required project files in a dedicated CAD project folder using the client's authorized file-editing tools. +5. Have it execute the saved project through Zoo MCP using `kcl_path` and inspect the geometry. +6. Open `main.kcl` in Zoo Design Studio and keep the KCL project as the editable deliverable. Request STEP or STL exports when needed. This is the practical benefit of Zoo MCP. You can stay inside the AI tool you already like while still checking the resulting CAD work in Zoo Design Studio. From 7f7b8b80a2f7e382d461aeaec4196e602c53b235 Mon Sep 17 00:00:00 2001 From: max Date: Mon, 14 Sep 2026 18:50:22 +0200 Subject: [PATCH 2/2] Keep the MCP walkthrough focused on delivering KCL --- content/pages/docs/developer-tools/mcp/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/pages/docs/developer-tools/mcp/index.mdx b/content/pages/docs/developer-tools/mcp/index.mdx index 1806e485..41877dd5 100644 --- a/content/pages/docs/developer-tools/mcp/index.mdx +++ b/content/pages/docs/developer-tools/mcp/index.mdx @@ -97,7 +97,7 @@ Here is a simple version using Codex or Claude Code: 3. Ask for something concrete, for example: "Create a simple mounting bracket with two bolt holes." 4. Have the assistant save `main.kcl` and any required project files in a dedicated CAD project folder using the client's authorized file-editing tools. 5. Have it execute the saved project through Zoo MCP using `kcl_path` and inspect the geometry. -6. Open `main.kcl` in Zoo Design Studio and keep the KCL project as the editable deliverable. Request STEP or STL exports when needed. +6. Deliver the saved KCL project. This is the practical benefit of Zoo MCP. You can stay inside the AI tool you already like while still checking the resulting CAD work in Zoo Design Studio.