aleleba/vectorcraft
1
0
Fork 0
mirror of https://github.com/storytold/vectorcraft.git synced 2026-10-24 17:56:50 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #4009 from dotCooCoo/fix/mcp-docs-start-installed-app

Browse Source 
MCP docs: start an installed app with the control port
This commit is contained in:
BFlat
2026-10-24 20:08:34 +07:00
committed by GitHub
parent 293dbcd534 eb4c5e7bf8
commit 8dc4f7ec6b
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/mcp.md
+16
View File
@@ -69,6 +69,22 @@ claude mcp add vectorcraft -- "C:\Program Files\VectorCraft\vectorcraft-cli.exe"
claude mcp add vectorcraft -- vectorcraft-cli mcp
```
For a live session, start the installed app with the control port before the MCP client starts the server:
```sh
# macOS: quit VectorCraft first, since `open -a` passes no arguments to an app that is already running
open -a VectorCraft --args --control 7979
# Windows (PowerShell), default install folder
& "C:\Program Files\VectorCraft\vectorcraft.exe" --control 7979
# Linux (deb, rpm)
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`.
## Confining file access
```sh