Is mcp configuration causing cmd issues

[Qaletx]

When I open the cursor, and then try to output cmd to open the command line window can not be opened, will be stuck, that is, will wait a while and then pop up the command line window, I suspect that this is caused by the MCP configuration, because I configured a number of local servers of MCP, they are all will be called out of the node to execute the command, I would like to ask whether this is the reason, in addition, for the need to configure the environment variables are as follows
D:\installed_soft\nvm\v20.18.3\node.exe D:\installed_soft\nvm\v20.18.3\node_modules@modelcontextprotocol\MCP\actors-mcp-server\dist\index.js

I need to configure an environment variable as TOKEN = xxxx, is this the right way to write this command (window environment)?

set TOKEN=xxxx D:\installed_soft\nvm\v20.18.3\node.exe D:\installed_soft\nvm\v20.18.3\node_modules@modelcontextprotocol\MCP\actors-mcp-server\dist\index.js

But it doesn’t seem to be working, which would be question 2

[Qaletx]

Question 1: After opening the cursor, there is a delay when opening the command line window. Sometimes, the already opened window may even freeze, and it only returns the translated text.
Question 2: I found that when everyone uses MCP, they are unable to access the remote MCP server using npx. The solution is to git clone it to the local machine, then run npm install and npm run build, and execute the project’s absolute path to build/index.js using the absolute path of Node. However, we know that an MCP service often requires creating environment variables and using --args parameters. How should this be written? I’m focusing on Windows here, like the following adify configuration. Everyone can try configuring it with cursor.
github：GitHub - apify/actors-mcp-server: Model Context Protocol (MCP) Server for Apify’s Actors
screenshot