Environment

• n8n version: 1.120.3
• n8n-nodes-mcp version: 0.1.29 (previously installed, attempting reinstallation)
• Installation method: n8n Community Node installation (manual reinstall after n8n upgrade)
• Node.js version: v22.18.0

Description
After upgrading my n8n instance from a previous version to v1.120.3, I'm unable to reinstall the n8n-nodes-mcp community node. The package had been installed and working correctly for months across multiple n8n upgrades, but fails on this latest version.

Error Message

Error installing new package
Error loading package "n8n-nodes-mcp": The specified package could not be loaded 
Cause: Package subpath './v3' is not defined by "exports" in /home/node/.n8n/nodes/node_modules/n8n-nodes-mcp/node_modules/zod/package.json

Steps to Reproduce

1. Upgrade n8n CE to v1.120.3
2. Uninstall n8n-nodes-mcp community node (standard practice during n8n upgrades)
3. Attempt to reinstall n8n-nodes-mcp via n8n Community Nodes interface
4. Installation fails with the above error

Expected Behavior
The package should install successfully, as it has during previous n8n version upgrades. According to PR #173, v0.1.29 includes dependency pinning that should prevent this exact error:

• @langchain/core pinned to 0.3.43
• zod pinned to 3.24.0
• npm overrides configured for consistent dependency resolution

Actual Behavior
Installation fails during dependency resolution, suggesting that n8n's community node installation process may not be respecting the package's overrides configuration or is experiencing conflicts with n8n v1.120.3's own dependency tree.

Additional Context

• Three other community nodes reinstalled successfully during this upgrade
• This is the only package experiencing installation issues
• The error specifically points to a zod version compatibility issue that PR Complete dependabot dependency updates with compatibility fixes #173 was intended to resolve
• npm package shows v0.1.29 as the latest published version (4 months ago)

Question
Is there a known compatibility issue between n8n v1.120.3 and n8n-nodes-mcp v0.1.29? Does n8n's community node installation process properly respect the overrides section in package.json?

Any guidance on a workaround or confirmation that this is a known issue would be greatly appreciated.

Relevant Links

• npm package: https://www.npmjs.com/package/n8n-nodes-mcp
• Fix PR: Complete dependabot dependency updates with compatibility fixes #173