Strongly hope to strengthen the support for Windows system environment。

[Archer456]

Hello, dear @smithery/cli developers?
When will it be compatible with the Windows operating system environment?
Currently, after installing the plug-in cline in Windows 11 system + pwsh7 + vscode 1.97.2,
it is not possible to successfully install and deploy mcp-server through the command "npx -y @smithery/cli@latest install @executeautomation/playwright-mcp-server --client cline". You must change the absolute path of node and the absolute path of "***\playwright-mcp-server\dist\index.js" in the mcp server configuration file of cline to connect to the mcp server?

Why is it so unfriendly to the Windows system? My other mbp does not have these problems under the macOS system. After npx -y @smithery/cli@latest install ***, mcpserver is automatically generated, and vscode automatically connects to the mcp server after saving the configuration.

[arjunkmrm]

hi @Archer456, we're releasing a beta version of a native smithery runner later today to fix windows compatibility issues, would you be interested to try it out?

[Archer456]

hi @Archer456, we're releasing a beta version of a native smithery runner later today to fix windows compatibility issues, would you be interested to try it out?

It would be great if it is fixed. This problem has hindered many people. If it is not fixed, I will give up the installation method of @smithery/cli@latest install.

[arjunkmrm]

Will comment in this thread when the native windows smithery/cli is ready later, you can try it out then

[arjunkmrm]

hi @Archer456, can you try this? We'll be adding the docs to our website as well. However, do note that support is currently only for smithery hosted servers. We're working on local support at the moment.

Step 1: Install Scoop

In windows powershell:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression

Step 2: Add Scoop to your PATH

$oldPath = [Environment]::GetEnvironmentVariable('Path', 'User') 

$newPath = $oldPath + ";$env:USERPROFILE\scoop\shims" 

[Environment]::SetEnvironmentVariable('Path', $newPath, 'User')

Step 3: Restart Powershell

Step 4: Check Scoop installation

scoop --version

Step 5: Install Smithery

scoop bucket add smithery https://github.com/smithery-ai/scoop-smithery

scoop install smithery

Step 6: Check smithery installation

smithery --help

Step 7: Install server

smithery install @smithery-ai/server-sequential-thinking --client claude

[Archer456]

hi @Archer456, can you try this? We'll be adding the docs to our website as well. However, do note that support is currently only for smithery hosted servers. We're working on local support at the moment.

Step 1: Install Scoop

In windows powershell:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Invoke-RestMethod -Uri https://get.scoop.sh | Invoke-Expression

Step 2: Add Scoop to your PATH

$oldPath = [Environment]::GetEnvironmentVariable('Path', 'User') 

$newPath = $oldPath + ";$env:USERPROFILE\scoop\shims" 
[Environment]::SetEnvironmentVariable('Path', $newPath, 'User')

Step 3: Restart Powershell

Step 4: Check Scoop installation

scoop --version

Step 5: Install Smithery

scoop bucket add smithery https://github.com/smithery-ai/scoop-smithery
scoop install smithery

Step 6: Check smithery installation

smithery --help

Step 7: Install server

smithery install @smithery-ai/server-sequential-thinking --client claude

hello I've found that it's possible to update to 1.1.40 now, did you fix the windows adaptation issue I mentioned in this version?

Regarding the way you mentioned scoop installing smithery, yes I use scoop as well, but I don't want to do it that way. Because I'm already using npm's way, I'm not sure if it will start an unexplained conflict with scoop's way if I don't do any cleanup or isolation. It's best for me to stay consistent with the npm way.

[Archer456]

oh,no 。This is still the case after updating to 1.1.40.

[Archer456]

Edit: Just saw your comment above

@Archer456 please try the new smithery's native runner which doesn't rely on npx anymore! Here are the docs: https://smithery.ai/docs/smithery-cli

The new commands would look like this:

smithery install @smithery-ai/server-sequential-thinking --client claude
smithery inspect @smithery-ai/server-sequential-thinking

Sorry, I found out something interesting.
Sorry, I tested something interesting.
Look below, both configurations can directly connect to mcp servers. 。 。
When I remove the two lines of configuration ""@smithery/cli@latest",
"run",". 。 。

{ "mcpServers": { "@executeautomation-playwright-mcp-server": { "command": "D:\\nodejs\\node.exe", "args": [ "D:\\nodejs\\node-global\\node_modules\\@executeautomation\\playwright-mcp-server\\dist\\index.js", "-y", "@smithery/cli@latest", "run", "@executeautomation/playwright-mcp-server", "--config", "\"{}\"" ], "autoApprove": [] }, "@kazuph-mcp-fetch": { "command": "D:\\nodejs\\node.exe", "args": [ "D:\\nodejs\\node-global\\node_modules\\@kazuph\\mcp-fetch\\dist\\index.js", "-y", "@smithery/cli@latest", "run", "@kazuph/mcp-fetch", "--config", "\"{}\"" ] } } }

{ "mcpServers": { "playwright": { "command": "D:\\nodejs\\node.exe", "args": [ "D:\\nodejs\\node-global\\node_modules\\@executeautomation\\playwright-mcp-server\\dist\\index.js", "-y", "@executeautomation/playwright-mcp-server", "--config", "\"{}\"" ], "autoApprove": [] }, "@kazuph-mcp-fetch": { "command": "D:\\nodejs\\node.exe", "args": [ "D:\\nodejs\\node-global\\node_modules\\@kazuph\\mcp-fetch\\dist\\index.js", "-y", "@kazuph/mcp-fetch", "--config", "\"{}\"" ] } } }

[arjunkmrm]

@Archer456 we released an update recently that should significantly improve support for windows. Seems to be a current limitation of the protocol's TS SDK. You can check out this open issue: modelcontextprotocol/typescript-sdk#101

[arjunkmrm]

@Archer456 updated to the latest MCP SDK (modelcontextprotocol/typescript-sdk#198), hope this fixes the spawn issues.
#77