It is not only MCP Servers, now Antigravity is not able to run the commands at all, because of PATH issue. Urgent update is needed, it is very hard to work with this way.
I am looking into issues with nvm and npm node installed with brew (i am on a mac), i found the gemini cli was using node globally installed with brew not nvm i uninstalled and am now on nvm only, still this has not resolved the issue but maybe someone much smarter than me can take this info and extrapolate a solution…. workaround
for me on the latest version using complete paths helps the issue for me seems to be a recent update using nvm to v24 of node.
“tech-lead-stack”: {
*"command"*: "/Users/bz3b/.nvm/versions/node/v24.14.1/bin/npm",
“args”: [
“–prefix”,
“/Users/bz3b/Desktop/repos/ai-dev/agent-toolbox/tech-lead-stack”,
“–silent”,
“run”,
“mcp:start”
\],
“env”: {
“PATH”: “/Users/bz3b/.nvm/versions/node/v24.14.1/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin”
}
},
```
It works for me, add it for all mcp servers configured in mcp_config.json
"env": {
"PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
},
Looks like now Google Antigravity is now loading $PATH using ~/.zshenv (I suppose to make it “lighter”?).
What did work for me for agent commands is adding node bin path (or whatever path we need) in .zshenv
Adding node bin path with one-liner:
echo “export PATH="$(dirname $(which node)):$PATH"” >> ~/.zshenv
For MCP servers currently we can stick with the env path workaround as mentioned from people earlier.
Regards!
Need resolution to the issue ASAP. Impacting the overall output.
This worked for me, the relative path works and saw no issues when referencing mcp’s. Once a patch / update is pushed for Antigravity, I would think these should be reverted. Solid temp fix. Thank you.
2 Likes
This is ridiculous. Antigravity seems to just be rotting away—always critical things breaking and very few useful features being added.
They need to get their shit together or everyone will be leaving for Claude code.
To fix:
Tell Opus 4.6 what the issue is, point it to this thread, and tell it to study up on your setup thoroughly before making any changes while asking you any verifying questions. Here’s what that resulted in in my case:
Created ~/.local/bin/npx-mcp — a wrapper script that:
-
Sources NVM (
~/.nvm/nvm.sh) to initialize the Node environment -
Looks up
npxvianvm which default -
Adds Node’s bin dir to PATH so
npxcan findnode -
Delegates to the real
npxwithexec
Updating ~/.zshenv with proper PATH doesn’t help. opening antigravity from terminal `open -a “Antigravity”`
1 Like
No official statement yet?! This is ridiculous!
I’ve bought the Pro plan recently and i will have to switch to another IDE if this continues like this in some days or so.
Hello,
Thank you for bringing the issue to our attention. Our engineering team is currently investigating the matter, and we appreciate your patience as we work toward a resolution.
2 Likes
I can confirm that the MCP error is gone after opening Antigravity from terminal but the terminal command completion is not working.
If you installed via Homebrew on MacOS, try this:
$PATH Fix
The root cause is that Antigravity’s non-interactive shell doesn’t source ~/.zshrc, so Homebrew’s /opt/homebrew/bin isn’t available. To fix globally, run once in your terminal:
bash
sudo ln -sf /opt/homebrew/bin/node /usr/local/bin/node
sudo ln -sf /opt/homebrew/bin/npm /usr/local/bin/npm
sudo ln -sf /opt/homebrew/bin/npx /usr/local/bin/npx
I use node and bun, manage node by n.
Use command: /usr/local/bin/npx is failed.
Use command: /Users/name/.bun/bin/bunx is ok.
After a brief conversation in Antigravity Agent Manager, I tried one suggestion on my Mac that seems to work. Use the agy command which exists in ~/.antigravity/antigravity/bin. I simply ran that command in my terminal to inherit the entire path:
Open terminal
Run agy
The symbolic suggestion above caused other errors
1 Like
MacOS (26.4.1 )
node installed via fnm
zsh
I’ve tried different workarounds, like opening Antigravity from terminal, edited ~/.zshenv (added fnm). None worked.
Moreover submitting feedback from Antigravity doesn’t work either.
Canceled subscription until it fixed.
I tried everything, the only thing that solved the problem was reverting to version 1.21.9.
1 Like
Hi all,
Antigravity 1.23.2 fix the problem (for dart) 
1 Like
For Stitch try this in terminal :
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash©
source ~/.zshrc
nvm install node
npx -v