feat: enable mcp to communicate with IDE via JSON-RPC server

[MaxKless]

• refactor: move socket utilities to shared library and add detection
• feat: create JSON-RPC client with content-length protocol compatibility
• refactor: remove NxIdeProvider in favor of IIdeJsonRpcClient
• add ide client and use it
• refactor mcp to be more dynamic
• support both ways for now
• talking between them works!!
• successful communication between vscode & stdio mcp
• ensure no stdio output
• formatting
• type cleanup

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 70b6e5a

Command	Status	Duration	Result
nx affected --targets=build,test,e2e-ci --confi...	✅ Succeeded	17m 3s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-07-31 15:06:19 UTC

[graphite-app]

The Windows named pipe path construction may cause issues with path length limitations. Windows named pipes should use a simpler naming convention. Consider modifying the path construction for Windows:

return platform() === 'win32' 
  ? '\\\\.\\pipe\\nx-console-' + createSimpleHash(workspaceRoot) 
  : path;

This approach uses a hash of the workspace root rather than embedding the full file path in the pipe name, which avoids potential path length issues while still maintaining uniqueness per workspace.

Suggested change

	export const getNxConsoleSocketPath = (workspaceRoot: string): string => {
	const path = resolve(join(getSocketDir(workspaceRoot), 'nx-console.sock'));
	return platform() === 'win32' ? '\\\\.\\pipe\\nx\\' + path : path;
	export const getNxConsoleSocketPath = (workspaceRoot: string): string => {
	const path = resolve(join(getSocketDir(workspaceRoot), 'nx-console.sock'));
	return platform() === 'win32' ? '\\\\.\\pipe\\nx-console-' + createSimpleHash(workspaceRoot) : path;
	};

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.