From 066d525425872d5daf0a97cf8051cef0cd61ffa7 Mon Sep 17 00:00:00 2001 From: dotCooCoo Date: Sat, 24 Oct 2026 07:27:58 -0700 Subject: [PATCH] MCP docs: wait for the app window, and the full --connect error `open -a` and PowerShell's `&` return before the app opens its control port, and `vectorcraft-cli mcp` tries the port only once, so the docs now say to wait for the VectorCraft window before starting the MCP client. The `--connect` failure is documented as the full line the CLI prints, `vectorcraft-cli: cannot connect to 127.0.0.1:7979: ` followed by the system's connection error. --- docs/mcp.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/mcp.md b/docs/mcp.md index 8461ed0c3..9ee0e1388 100644 --- a/docs/mcp.md +++ b/docs/mcp.md @@ -83,7 +83,10 @@ vectorcraft --control 7979 The Dock, Start menu and desktop launchers start the app without `--control`, so the app opens no control port unless `VECTORCRAFT_CONTROL_PORT` is set. `vectorcraft-cli mcp` with no flag tries `127.0.0.1:7979` once, when it starts: a server that started before the app stays headless until the MCP client restarts -it. With `--connect`, a server that finds no app stops with `cannot connect to 127.0.0.1:7979`. +it. `open -a` and PowerShell's `&` return before the app opens the port, so wait until the VectorCraft +window is open before you start the MCP client. With `--connect`, a server that finds no app stops and +prints `vectorcraft-cli: cannot connect to 127.0.0.1:7979: ` followed by the system's connection error, for +example `connection timed out`. ## Confining file access