Windows: MCP entries start through cmd /c npx or bun cli/index.ts (npx.cmd and the sh launcher cannot be spawned, pitfall 94); desktop download streams with progress and fails after 60 s without data (pitfall 95); getting-started Windows note
This commit is contained in:
parent
e5dffb5533
commit
0ac3cd02b0
6 changed files with 77 additions and 9 deletions
|
|
@ -152,6 +152,10 @@ plain Markdown and the CLI is a normal command.
|
|||
and `--command "<cmd>"` to choose how the MCP server starts. It only adds or updates the `storebound` entry and its
|
||||
own skill folders; everything else in those files stays as it is, and re-running it is safe.
|
||||
|
||||
**Windows:** an MCP client cannot start `npx` directly (it is `npx.cmd`). `install` writes the working form for you;
|
||||
by hand use `"command": "cmd", "args": ["/c", "npx", "-y", "storebound@<version>", "mcp"]` (or `bunx storebound mcp`
|
||||
with Bun). If the server shows "connection closed", check this first ([pitfall 94](../skills/store-pitfalls/SKILL.md)).
|
||||
|
||||
---
|
||||
|
||||
[All docs](README.md) · [README](../README.md)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue