From 8a2dad009255fcba65665e0ebd80889c01d237d5 Mon Sep 17 00:00:00 2001 From: ispyisail Date: Tue, 29 Sep 2026 12:45:03 +1300 Subject: [PATCH] mcp_server: QET_BINARY fallback order matches the code (install, then PATH) --- ai_assistants.md | 2 +- mcp_server.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ai_assistants.md b/ai_assistants.md index 49736cc..c0245a2 100644 --- a/ai_assistants.md +++ b/ai_assistants.md @@ -63,7 +63,7 @@ explicitly. They go to a new file you name. > is when it asks. This section will drop this notice once the PR lands. Exports and edits start QElectroTech in the background. The server finds it -from `QET_BINARY`, or from `qelectrotech` on your `PATH`. The assistant +from `QET_BINARY`, else from `qelectrotech` on your `PATH`. The assistant cannot pick another program. --- diff --git a/mcp_server.md b/mcp_server.md index 0a9dcef..429dbe6 100644 --- a/mcp_server.md +++ b/mcp_server.md @@ -246,7 +246,7 @@ and a call cannot choose: | Variable | Effect | |---|---| -| `QET_BINARY` | the QElectroTech the tools launch. Without it: `qelectrotech` on `PATH`, else the installation the server sits in (`/share/qelectrotech/mcp/qet_mcp.py`) | +| `QET_BINARY` | the QElectroTech the tools launch. Without it: the installation the server sits in (`/share/qelectrotech/mcp/qet_mcp.py`), else `qelectrotech` on `PATH` | | `QET_MCP_BINARIES` | other executables a call may name as `binary`, separated like `QET_MCP_WORKSPACE` — for comparing two builds | | `QET_MCP_ALLOW_ANY_BINARY=1` | turns the check off: a call can then run any program | | `QET_MCP_ELEMENTS` | element collections a call may name as `elements_dir`, besides the workspace and the installed one |