Hi all!
I am aware that MCP has only been covered for Windsurf and Cursor, but I figured it would not be an issue to port to WSL through VS Code.
I am giving the command to the MCP: Add Server command of VS Code, and the following is generated:
"mcp": {
"servers": {
"appwrite": {
"type": "stdio",
"command": "env",
"args": [
"APPWRITE_API_KEY=standard_35******",
"env",
"APPWRITE_PROJECT_ID=67******",
"uvx",
"mcp-server-appwrite",
"--databases",
"--users"
]
}
}
},
This causes this error:
2025-04-14 16:40:47.649 [info] Starting server appwrite
2025-04-14 16:40:47.650 [info] Connection state: Starting
2025-04-14 16:40:47.663 [info] Starting server from LocalProcess extension host
2025-04-14 16:40:47.681 [info] Connection state: Starting
2025-04-14 16:40:47.683 [info] Connection state: Error spawn env ENOENT
I tried changing the generated config as follows:
"appwrite": {
"command": "uvx",
"args": [
"mcp-server-appwrite",
"--databases",
"--users"
],
"env":{
"APPWRITE_API_KEY": "standard_3*******",
"APPWRITE_PROJECT_ID": "675*******"
}
}
When ran, I get this output:
2025-04-14 16:42:13.937 [info] Starting server appwrite
2025-04-14 16:42:13.937 [info] Connection state: Starting
2025-04-14 16:42:13.949 [info] Starting server from LocalProcess extension host
2025-04-14 16:42:13.963 [info] Connection state: Starting
2025-04-14 16:42:13.965 [info] Connection state: Error spawn uvx ENOENT
uvx is indeed installed.
$ uvx
Provide a command to run with `uvx <command>`.
What am I doing wrong here?
TL;DR
The developer is trying to use MCP on VS Code for a WSL port but is encountering errors related to spawn env ENOENT and spawn uvx ENOENT. They have tried alternative configurations without success. The issue may be due to incorrect command or path configurations. To address this, ensure that the paths to env and uvx are correctly specified in the VS Code configuration.
