Back
mcp on VS Code not working
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:
TypeScript
"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:
TypeScript
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:
TypeScript
"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:
TypeScript
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.
TypeScript
$ uvx
Provide a command to run with `uvx <command>`.
What am I doing wrong here?
TL;DR
Developers are having issues with the MCP on VS Code. The error "spawn env ENOENT" is occurring when trying to start the server. Changing the configuration to use "env" directly may not work. Consider setting the environment variables directly in the config file and modifying the command structure.