I can run npx -y @smithery/cli@latest run @smithery-ai/server-sequential-thinking --config “{}” normally in the command line, but when I add MCP to the cursor, it shows as not working
Hey, that’s strange. The command you provided doesn’t work for me either, but if I copy it here, it works:
The commands I provided might have encoding issues when you copy them, but I copied them directly from Sequential Thinking MCP Server | Smithery into the cursor and it doesn’t work either.
Because I’m in China, I might need to use a VPN. I can access CMD because I’m using Proxifier to proxy two domains: *.run.app; *.smithery.ai, so it works normally. But the cursor probably didn’t go through the proxy program correctly, so it doesn’t work 
I think in this case you might need a VPN, or try setting up a proxy for your network.
It should be like this, my CMD can work normally because I used Proxifier proxy, but the cursor can’t probably go through the proxy process because I’m not a global VPN
你弄好了吗?
Haven’t solved it yet, if anyone has a solution, please tell us 
I have the same issue. I can’t get anything to work with npx. Only node works as a command.
The current workaround is to download it locally and run it with node
Example:
npm install -g @modelcontextprotocol/server-sequential-thinking
Then find index.js like mine
node D:\software\nvmnode\node_modules@modelcontextprotocol\server-sequential-thinking\dist\dist\index.js
Then add it to the cursor
3 Likes
wait so this is running on your local as a daemon? I am curious if I can just spin up the instances (dockerized) versions and point to it. Can anyone verify if having a different OS has impact success of using the MCP?
I’m on WIN, anyway I can’t use NPX on https://smithery.ai/, but the last method I provided can use MCP normally 
yeah I am about to try it. I prefer using a docker, I will play around with and report back if I can get something up.
yeah figured it out. You can just fork the entire MCP server file, run npm install and then mv to each server file you want to use, run the npm build and then copy the path to MCP, then type node {filepath}. I got it to work. More steps but it works.
I ran into this issue, and it took me far too long to solve because I’m not a Node.js developer.
Do you use NVM to manage your Node versions? I’m going to assume you use some kind of package manager.
And maybe you have a fancy setup in your terminal like I did?
Make sure you NVM_DIR gets set in your .zshrc file, so that when your integratedTerminal in the IDE runs ‘/bin/zsh -l’, it won’t load .zshenv or .zprofile, but it will load .zshrc. Here’s what I put at the end of mine:
if [[ -z "{NVM_DIR}" ]]; then
export NVM_DIR="${HOME}/.nvm"
fi
[ -s "${NVM_DIR}/nvm.sh" ] && \. "${NVM_DIR}/nvm.sh"
I swear, I was banging my head against the wall for weeks trying to figure out why…and it was that simple. And now most of my MCP servers are working fine with the npx instructions.
it works, thanks