[BUG] Claude Desktop 1.0.734: MCP servers fail to initialize - 'Cannot read properties of undefined (reading cmd)'
Resolved 💬 26 comments Opened Nov 15, 2025 by vimholic Closed Nov 30, 2025
💡 Likely answer: A maintainer (catherinewu, contributor)
responded on this thread — see the highlighted reply below.
Bug Description
Claude Desktop version 1.0.734 fails to initialize all MCP servers with a JavaScript runtime error, making MCP functionality completely unusable.
Error Message
Cannot read properties of undefined (reading 'cmd')
Stack Trace:
TypeError: Cannot read properties of undefined (reading 'cmd')
at C:\Users\primus\AppData\Local\AnthropicClaude\app-1.0.734\resources\app.asar\.vite\build\index.js:211:8256
at async C:\Users\primus\AppData\Local\AnthropicClaude\app-1.0.734\resources\app.asar\.vite\build\index.js:211:6757
Environment
- OS: Windows 11
- Claude Desktop Version: 1.0.734 (released 2025-11-15)
- Previous Working Version: 1.0.332 (released 2025-11-06)
- Log File:
%APPDATA%\Claude\logs\mcp-server-*.log
Steps to Reproduce
- Install Claude Desktop 1.0.734 (latest version as of 2025-11-15)
- Configure any MCP server in
%APPDATA%\Claude\claude_desktop_config.json:
``json``
{
"mcpServers": {
"cdn-billing": {
"command": "python",
"args": ["C:\\path\\to\\mcp_proxy.py"],
"env": {
"MCP_HOST": "localhost",
"MCP_PORT": "8765"
}
}
}
}
- Restart Claude Desktop
- Check logs at
%APPDATA%\Claude\logs\mcp-server-cdn-billing.log
Expected Behavior
MCP server should initialize successfully and tools should be available in Claude Desktop.
Actual Behavior
- MCP server initialization fails immediately
- Error appears in logs:
Cannot read properties of undefined (reading 'cmd') - No MCP tools are available
- Same configuration worked perfectly in version 1.0.332
Impact
CRITICAL: All MCP servers fail to initialize in version 1.0.734
This affects:
- All users who updated to 1.0.734
- All new installations (1.0.734 is currently the latest distributed version)
- Any custom MCP servers regardless of configuration
Workaround
Downgrade to version 1.0.332:
PowerShell:
# Stop Claude Desktop
taskkill /F /IM claude.exe /T
# Remove broken version
Remove-Item -Path "$env:LOCALAPPDATA\AnthropicClaude\app-1.0.734" -Recurse -Force
Remove-Item -Path "$env:LOCALAPPDATA\AnthropicClaude\packages\AnthropicClaude-1.0.734.nupkg" -Force
# Disable auto-update
Rename-Item -Path "$env:LOCALAPPDATA\AnthropicClaude\Update.exe" -NewName "Update.exe.disabled"
# Start working version
Start-Process "$env:LOCALAPPDATA\AnthropicClaude\app-1.0.332\claude.exe"
Additional Context
- This bug was discovered while deploying MCP servers to production
- Version 1.0.734 is still being distributed as the latest version at
https://downloads.claude.ai/releases/win32/x64/RELEASES - The error occurs during MCP configuration parsing, suggesting a regression in the configuration validation code
- No configuration changes work - the bug affects all MCP server configurations
- Verified that 1.0.332 works with identical configuration
Severity
High - Breaks all MCP functionality for Windows users on latest version
Showing cached comments. Read the full discussion on GitHub ↗
25 Comments
I can confirm same issue as described.
I can also confirm this issue.
also having the same issue on my side
Same Issue
Same Issue
I can also confirm this issue. Happened as soon as Claude desktop upgraded (broke) and when downgrading it fixes it with exact MCP configuration json.
Can also confirm I am experiencing this issue.
+1 Confirm
Same here. I just installed for the first time so the workaround of reverting to an older version does not work for me.
Same Issue Claude 1.0.734 (b8f837) 2025-11-14T18:56:13.000Z
Same issue.
Same issue.
This is a new computer and I do not have access to previous version locally.
How can I downgrade without a local version available?
Same issue.
can confirm bug as well - same issue - downgrading workaround also confirmed as working
Downgraded on Windows using
wingetHow can I disable auto update ?
Same issue. Had to downgrade, thanks @conradj5 for your tip!
Thanks @conradj5 for your tip! However, it does not work for me. I used this command:
Also, I renamed the
Update.exeto prevent the automaic update.Thanks for reporting. This seems like an issue with Claude Desktop and the Claude Desktop team will be releasing a hypothesized fix tomorrow. Closing since this is the Claude Code repo and I don't think this is an issue with Claude Code
Hey folks, thanks for reporting, as mentioned above we should have a hypothesized fix out for this soon.
To help us verify / identify the issue here, can someone who was experiencing this issue run
where pythonin cmd orGet-Command pythonin powershell.Also interested in the
python3variants.Last Claude Desktop release 1.0.1307 fix it
Hi all, we've released an update containing an expected fix, pls post here if you still encounter any issues. thanks!
New error:
Error: spawn uv ENOENT
Confirmed fixed in v1.0.1405!
Environment:
Test Results:
Thank you for the quick fix! The update resolved the issue completely.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.