›_ Claude Code Issues
Claude Code Issues / #4195

[BUG]

Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 8 comments · opened Jul 23, 2025 · closed Jul 23, 2025

Environment

  • Platform (select one):
  • [x] Other: Claude Desktop with MCP (Desktop Commander)
  • Claude CLI version: N/A (Using Claude Desktop 0.12.28)
  • Operating System: macOS 15 (Sequoia) on M1 iMac
  • Terminal: Terminal.app

Bug Description

Desktop Commander MCP is throwing "Cannot convert undefined or null to object" errors on all file system and process operations, making the tool unusable. The error affects multiple tool categories systematically, suggesting a parameter serialization issue in the MCP protocol layer.

Steps to Reproduce

  1. Configure Desktop Commander in Claude Desktop MCP settings with NPX
  2. Restart Claude Desktop completely
  3. Attempt any file system operation: list_directory("/Users")
  4. Attempt any process operation: start_process("echo test", 5000)
  5. Both fail with "Cannot convert undefined or null to object"

Expected Behavior

  • Directory listings should return file/folder contents
  • Process operations should execute and return output
  • File operations should read/write successfully

Actual Behavior

All operations fail immediately with the object conversion error. Basic configuration access (get_config) works, but all file system, process, and editing operations fail systematically with "Error executing code: Cannot convert undefined or null to object".

Additional Context

  • Desktop Commander Version: 0.2.6
  • Operating System: macOS 15 (Sequoia) on M1 iMac
  • Claude Desktop Version: Claude 0.12.28 (5f9bc7) 2025-07-18T21:14:50.000Z
  • Node.js Version: v24.2.0
  • NPM Version: 11.3.0
  • Installation Method: NPX via Claude Desktop MCP config

Current Configuration

"desktop-commander": {
  "command": "npx",
  "args": [
    "-y",
    "@wonderwhy-er/desktop-commander@latest"
  ]
}

Error Details

Error Message

Error executing code: Cannot convert undefined or null to object

Affected Operations

  • ❌ list_directory - All directory listing operations fail
  • ❌ start_process - Cannot start any terminal processes
  • ❌ edit_block - File editing operations fail
  • ❌ read_file - File reading operations fail
  • ✅ get_config - Basic configuration access works

Error Statistics

  • Total Tool Calls: 894
  • Failed Calls: 81 (9.1% failure rate)
  • Pattern: Systematic failure across multiple tool types, not isolated to specific operations

Steps to Reproduce

  1. Configure Desktop Commander in Claude Desktop MCP settings
  2. Restart Claude Desktop
  3. Attempt any file system operation: list_directory("/Users")
  4. Attempt any process operation: start_process("echo test", 5000)
  5. Both fail with "Cannot convert undefined or null to object"

Expected Behavior

  • Directory listings should return file/folder contents
  • Process operations should execute and return output
  • File operations should read/write successfully

Actual Behavior

All operations fail immediately with the object conversion error, suggesting a parameter serialization issue in the MCP protocol layer.

Troubleshooting Attempted

  1. ✅ Added -y flag to NPX command to prevent installation prompts
  2. ✅ Restarted Claude Desktop completely
  3. ✅ Verified configuration syntax is correct
  4. ❌ Error persists across all troubleshooting attempts

Technical Analysis

The error "Cannot convert undefined or null to object" typically occurs when JavaScript tries to:

  • Use Object.keys(), Object.entries(), or Object.assign() on undefined/null values
  • Iterate over properties of undefined/null objects
  • Perform operations expecting an object but receiving undefined/null

This suggests the issue is in parameter handling/serialization between Claude Desktop and Desktop Commander, where expected object parameters are arriving as undefined or null.

Potential Root Causes

  1. MCP Protocol Version Mismatch: Desktop Commander 0.2.6 may be incompatible with current Claude Desktop MCP implementation
  2. Parameter Serialization Issue: Objects not being properly serialized/deserialized in the MCP transport layer
  3. Configuration Issue: Despite correct syntax, parameters may not be properly structured for the current version

Suggested Investigation Areas

  1. Check parameter validation logic in Desktop Commander's MCP handler
  2. Verify object destructuring/property access in tool implementations
  3. Review MCP protocol compatibility between versions
  4. Test with alternative installation methods (global npm install vs npx)

Additional Context

  • Multiple MCP servers in the same environment work correctly (filesystem, applescript-automation, etc.)
  • Basic Desktop Commander connection works (get_config succeeds)
  • The issue appears specific to operations requiring parameter processing
  • Error is consistent and reproducible across all affected operations

Workaround Needed

Currently no workaround available - the tool is completely unusable for file system and process operations.

Original post on MCP site https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/193#issuecomment-3106116048 but now it seems that many MCP's are failing with the new desktop app.

---

Priority: High - Complete loss of functionality for primary use cases

View original on GitHub ↗

8 Comments

tommysnello · 1 year ago

same problem for me

Heggeg · 1 year ago

I get exact the same problems like u. (win,mac,linux, max 20x)

etlmwwn · 1 year ago

Same issue, and only appeared today 23rd July 2025, with both server-filesystem previously installed + the "Extensions" add in, which is now available in the UI, but is still "Underneath the hood, it uses @modelcontextprotocol/server-filesystem"

Environment
Platform (select one):

Other: Claude Desktop with MCP (Desktop Commander)
Claude CLI version: N/A (Using Claude Desktop Claude 0.12.28 (5f9bc7) 2025-07-18T21:14:50.000Z)
Operating System: Windows 11 ARM64 Snapdragon Windows Suface Pro 7
Terminal: Ubuntu WSL

Bug Description

Desktop Commander MCP is throwing "Cannot convert undefined or null to object" errors on some file system and process operations, at times it works intermitantly, at other times not at all, making the tool unusable as well as locking up entirely, requiring a "Task Manager" kill process to restart it.

<img width="1132" height="678" alt="Image" src="https://github.com/user-attachments/assets/866690fc-a109-4c75-b626-7dcb61ce6f34" />

{
"mcpServers": {
"filesystem": {
"command": "wsl.exe",
"args": [
"-d",
"Ubuntu",
"bash",
"-c",
"DEBUG=* npx -y @modelcontextprotocol/server-filesystem /home/path/path
]
}
}
}

Troubleshooting Attempted

  • Re-installed Claude Desktop Windows
  • Changed between "Extension" through the the UI, and the older manual JSON config for the MCP
  • Cleared logs / Cleared Cache and Restarted (through Claude Desktop UI > Menu > Help > Trhoubleshooting)
DannyJanmaat · 1 year ago

DETAILED ROOT CAUSE ANALYSIS - Anthropic Infrastructure Backend Regression

REFINED BUG CHARACTERIZATION

After extensive investigation including client backup analysis, we have definitively identified this as a server-side regression introduced by Anthropic on July 23, 2025.

EXACT FAILURE PATTERN

  • 1st MCP tool call in conversation: Always succeeds
  • 2nd+ MCP tool calls in conversation: Always fail with "Cannot convert undefined or null to object"
  • New conversation: Pattern resets - 1st call works again

This is NOT random - it's 100% reproducible and deterministic.

PLATFORM & SUBSCRIPTION TIER INFORMATION

Confirmed Affected Platforms:

  • ✅ Windows: Extensive testing and multiple user reports
  • ✅ macOS: Multiple GitHub issue confirmations (#4195, #4197)
  • ✅ Linux (WSL Ubuntu 22.04): Direct testing confirms Claude Code CLI failures with same backend infrastructure

DEFINITIVE CROSS-PLATFORM VALIDATION:
WSL Ubuntu Linux Testing Results:

  • ✅ Network Connectivity: curl tests to api.anthropic.com (2607:6bc0::10) successful
  • ✅ SSL/TLS Handshake: Perfect connectivity to Anthropic ASN 399358 infrastructure
  • ❌ Claude Code CLI: Systematic TypeError (fetch failed) on all API calls
  • ✅ Authentication: Login process succeeds
  • ❌ Application Function: Complete API communication failure identical to Windows testing
  • Conclusion: Cross-platform infrastructure regression confirmed across Windows, macOS, and Linux

DEFINITIVE CROSS-SUBSCRIPTION TIER VALIDATION:

  • ✅ Claude Max Plan: Original extensive testing confirmed affected
  • ✅ Claude Pro Plan: New account testing confirms identical crash pattern
  • Pattern Confirmed: Backend regression affects ALL subscription tiers
  • Real-time Correlation: Testing conducted during Anthropic's acknowledged "temporary service disruption"
  • Conclusion: Infrastructure-wide regression impacting entire customer base

This comprehensive cross-platform and cross-tier validation definitively proves the backend regression affects Anthropic's entire infrastructure and customer base.

---

COMMUNITY VALIDATION & REAL-TIME CONFIRMATION

GitHub Issues Confirmation

This analysis has been validated by multiple independent user reports:

  • Issue #4195: macOS M1 iMac - Desktop Commander failures
  • Issue #4197: macOS - @modelcontextprotocol/server-filesystem failures
  • Issue #4192: Windows - Reports both Claude Code and Claude Desktop affected
  • Cross-platform confirmation: Users on Windows, macOS reporting identical symptoms

REAL-TIME SERVICE DISRUPTION CORRELATION

Critical Evidence: During cross-subscription tier testing, Anthropic simultaneously acknowledged:

  • Status Page Alert: "Claude will return soon"
  • Service Disruption: "Claude.ai is currently experiencing a temporary service disruption"
  • Perfect Timing Correlation: Testing conducted during active service disruption
  • Immediate Application Crashes: Complete Claude Desktop failure after first MCP call

Community Timeline Consensus

Multiple users independently confirm July 23, 2025 as the emergence date:

  • "only appeared today 23rd July 2025" (etlmwwn)
  • "same problem for me" (tommysnello)
  • "exact the same problems like u. (win,mac,linux, max 20x)" (Heggeg)

Escalating Failure Pattern Validation

Community reports and comprehensive cross-subscription testing confirm escalating severity:

  • Initial Reports: Parameter-based calls fail with "Cannot convert undefined or null to object"
  • Max Plan Evidence: Detailed logs show first call with correct arguments object, second call missing arguments
  • Pro Plan Validation: Identical pattern confirmed with real-time logs during service disruption
  • Current State: Complete application crashes after first MCP tool call in some scenarios
  • JSON Processing Failures: Backend sending malformed JSON responses across all subscription tiers
  • Cross-subscription Impact: Both Pro and Max plan users experiencing identical technical failures with matching log patterns

---

ROOT CAUSE CONFIRMED: CLAUDE DESKTOP BACKEND-SPECIFIC REGRESSION

ROOT CAUSE CONFIRMED: ANTHROPIC BACKEND REGRESSION

We analyzed client backup data and confirmed NO client-side changes occurred between the working state (July 22) and broken state (July 23).

CLAUDE CODE CLI STATUS - CONFIRMED API FAILURES:

  • Network connectivity to Anthropic API (2607:6bc0::10) confirmed working via curl test
  • Authentication successful: User login and session establishment works
  • API calls consistently fail: TypeError (fetch failed) on all requests
  • Same failure pattern with and without Claude Desktop running
  • Application-level regression: Basic connectivity works, but API calls fail
  • Same backend infrastructure as Claude Desktop (ASN 399358)
  • Unable to test MCP functionality due to underlying API communication failures
  • Issue #4192 reports appear accurate - Claude Code CLI experiencing systematic failures

VS Code with Claude Sonnet 3.7 remains fully functional with local MCP servers, definitively proving this is primarily a Claude Desktop backend-specific issue rather than a universal Anthropic platform bug.

NETWORK ANALYSIS CONFIRMS DIFFERENT BACKENDS:

Comprehensive network monitoring revealed completely different backend infrastructures:

Claude Desktop Network Endpoints:

  • Anthropic Own Infrastructure: 2607:6bc0::10 (ASN 399358 - ANTHROPIC)
  • AWS EC2: ec2-18-97-36-54.compute-1.amazonaws.com, ec2-18-97-36-70.compute-1.amazonaws.com
  • Google Cloud: 103.57.36.34.bc.googleusercontent.com

VS Code Claude Network Endpoints:

  • GitHub: lb-140-82-114-21-iad.github.com, lb-140-82-112-22-iad.github.com
  • Microsoft Azure: 51.116.246.106, 13.107.5.93, 51.105.71.136, 20.42.65.85
  • AI Services: 4.225.11.192 (possibly ChatGPT/CoPilot/Meta routing)
  • Microsoft IPv6: 2603:1061:10::16, 2620:1ec:29:1::67, 2620:1ec:bdf::67

ZERO ENDPOINT OVERLAP between Claude Desktop and VS Code confirms completely separate backend pathways.

TIMELINE EVIDENCE

July 22, 2025 (Working State):

  • MCP functioning normally through 22:40 PM
  • Client files unchanged since July 19
  • No Squirrel update activity

July 23, 2025 (Broken State):

  • MCP bug manifests with identical client
  • All client versions (0.7.9, 0.12.19, 0.12.28) exhibit same behavior
  • No client updates or configuration changes

CLIENT BACKUP ANALYSIS

BACKUP DATA (July 22 working state):
- Update.exe: July 19, 1:22 AM  
- squirrel.exe: July 19, 1:22 AM
- NO Squirrel-CheckForUpdate.log present
- Last normal activity: July 22, 22:40 PM

CONCLUSION: Zero client changes between working and broken states

---

TECHNICAL MANIFESTATION

The bug manifests in Anthropic's backend incorrectly generating MCP protocol calls and JSON responses:

1st Call (PARTIAL SUCCESS) - Correct MCP Protocol:

{
  "method": "tools/call",
  "params": {
    "name": "write_file",
    "arguments": {
      "path": "D:\\TEST\\alt1.txt",
      "content": "test content"
    }
  },
  "jsonrpc": "2.0",
  "id": 24
}

2nd+ Calls (COMPLETE FAILURE) - Missing Arguments Object:

{
  "method": "tools/call",
  "params": {
    "name": "write_file"
  },
  "jsonrpc": "2.0",
  "id": 25
}

CRITICAL: Backend JSON Processing Corruption
Client logs reveal systematic JSON parsing failures:

SyntaxError: Unexpected non-whitespace character after JSON at position 120 (line 1 column 121)

SEVERE ESCALATION: Complete Application Crashes
Recent testing shows the regression has escalated from MCP-specific failures to complete Claude Desktop application crashes after the first MCP tool call, requiring full application restart.

MCP SERVER ERROR RESPONSE:

{
  "error": {
    "code": "invalid_type",
    "expected": "object", 
    "received": "undefined",
    "path": [],
    "message": "Required"
  }
}

---

COMPREHENSIVE TESTING RESULTS

COMPREHENSIVE MCP SERVER TESTING

All MCP server types exhibit identical behavior in Claude Desktop:

  • Custom Rust MCP implementation: Same 1st-call-works, 2nd+-calls-fail pattern
  • Desktop Commander: Standard MCP server - same failure pattern
  • File server: Additional MCP server - same failure pattern
  • Claude Desktop Extensions: Native Desktop Extensions - same failure pattern

CRITICAL: The exact same MCP servers work perfectly in VS Code with Claude Sonnet 3.7, definitively proving the MCP server implementations are correct and the bug is exclusively in Claude Desktop's backend MCP request generation.

  • All Tool Types Affected: With parameters, without parameters - all fail after 1st call
  • All Models Affected: Sonnet 4, Sonnet 3.7 - same behavior
  • All Client Versions Affected: 0.7.9, 0.12.19, 0.12.28 - identical behavior
  • Consistent Across Sessions: Restarting Claude Desktop doesn't fix existing conversations
  • Claude Code CLI Status: CONFIRMED SYSTEMATIC API FAILURES
  • Network connectivity to ASN 399358 infrastructure verified working
  • Authentication and session establishment successful
  • All API calls fail with TypeError (fetch failed)
  • Issue #4192 reports confirmed accurate through direct testing
  • Complete application dysfunction - unable to process any user requests
  • VS Code Claude Confirmed Unaffected: Claude Sonnet 3.7 with local MCP servers works perfectly
  • Conclusion: Comprehensive infrastructure regression affecting all Anthropic-owned clients routing through ASN 399358

CONVERSATION-SPECIFIC STATE CORRUPTION

  • Per-conversation bug: Each new conversation gets exactly 1 working MCP call
  • State persistence: Failed conversations remain broken indefinitely
  • No global corruption: New conversations work normally (for 1 call)

---

TECHNICAL ANALYSIS

BUG TYPE: Claude Desktop Backend Post-First-Call MCP Processing Regression

What happens:

  1. Claude Desktop backend correctly processes the 1st MCP tool call request
  2. After 1st successful call, Desktop-specific backend MCP processing logic becomes corrupted
  3. Subsequent tool call requests fail to include the required "arguments" object
  4. MCP servers correctly reject malformed calls due to missing required parameters

ARCHITECTURE INSIGHT:
Network analysis reveals Claude Desktop uses Anthropic's own infrastructure (ASN 399358) supplemented by AWS and Google Cloud services, while VS Code uses Microsoft/GitHub infrastructure with Azure and AI service routing. Since both Claude Code CLI and VS Code with Claude Sonnet 3.7 remain fully functional with MCP servers while Claude Desktop exhibits the bug across all versions, this definitively proves a regression in Anthropic's own backend infrastructure serving Claude Desktop specifically.

BACKEND INFRASTRUCTURE COMPARISON:

  • Claude Desktop: Anthropic Infrastructure (ASN 399358) + AWS EC2 + Google Cloud → BROKEN MCP
  • Claude Code CLI: Anthropic Infrastructure (ASN 399358) → BROKEN API CALLS
  • VS Code Claude: Microsoft Azure + GitHub + AI Service Routing → WORKING MCP

Critical Insight: BOTH Anthropic-owned clients (Desktop + Code CLI) routing through ASN 399358 are experiencing failures, while VS Code Claude using Microsoft/GitHub infrastructure remains functional. This provides definitive evidence of a backend regression in Anthropic's own infrastructure.

NOT AFFECTED BY:

  • MCP server implementations
  • Claude Desktop client version
  • Parameter content or complexity
  • Desktop configuration or installation
  • Windows environment settings
  • Network/firewall configurations

ROOT CAUSE LOCATION:

Anthropic's own backend infrastructure (ASN 399358) - specifically the infrastructure that serves Claude Desktop exclusively. Network analysis confirms Claude Desktop connects to 2607:6bc0::10 (owned by Anthropic) and associated AWS/Google Cloud services, while VS Code uses Microsoft/GitHub infrastructure. The MCP regression is isolated to Anthropic's own backend infrastructure deployed on July 23, 2025.

---

EVIDENCE FROM CLIENT LOGS

File: %APPDATA%\Roaming\Claude\logs\mcp.log

Original Max Plan Testing:

2025-07-23T15:10:50.621Z [info] [desktop-commander] Message from client: 
{"method":"tools/call","params":{"name":"write_file","arguments":{"path":"D:\\TEST\\alt1.txt","mode":"rewrite","content":"alternative syntax test"}},"jsonrpc":"2.0","id":24}

2025-07-23T15:10:50.627Z [info] [desktop-commander] Message from server: 
{"jsonrpc":"2.0","id":24,"result":{"content":[{"type":"text","text":"Successfully wrote to D:\\TEST\\alt1.txt (1 lines) "}]}}

2025-07-23T15:10:59.630Z [info] [desktop-commander] Message from client: 
{"method":"tools/call","params":{"name":"write_file"},"jsonrpc":"2.0","id":25}

2025-07-23T15:10:59.633Z [info] [desktop-commander] Message from server: 
{"jsonrpc":"2.0","id":25,"result":{"content":[{"type":"text","text":"Error: [\n  {\n    \"code\": \"invalid_type\",\n    \"expected\": \"object\",\n    \"received\": \"undefined\",\n    \"path\": [],\n    \"message\": \"Required\"\n  }\n]"}],"isError":true}}

Pro Plan Validation Testing:

2025-07-23T16:58:41.378Z [info] [Windows-MCP] Message from client: 
{"method":"tools/call","params":{"name":"State-Tool","arguments":{"use_vision":true}},"jsonrpc":"2.0","id":7}

2025-07-23T16:58:43.727Z [info] [Windows-MCP] Message from server: 
{"jsonrpc":"2.0","id":7,"result":{"content":[{"type":"text","text":"Error calling tool 'State-Tool': 'Taskbar'"}],"isError":true}}

CROSS-SUBSCRIPTION TIER PATTERN CONFIRMATION:
Both Max Plan and Pro Plan logs show identical backend behavior:

  • ✅ First calls include correct arguments object
  • ❌ Subsequent calls demonstrate systematic backend failures
  • ✅ MCP protocol communication remains intact (tools/list, resources/list successful)
  • ❌ Tool execution failures occur regardless of subscription tier

Clear evidence: Anthropic's backend stops generating the "arguments" object after the first successful call across all subscription tiers.

---

CLIENT BACKUP VERIFICATION & NETWORK ANALYSIS

Backup Analysis Commands:

# Confirmed: No client updates between July 22-23
Get-ChildItem "C:\Users\...\AppData\Local\AnthropicClaude.oud\" -Recurse | 
  Where-Object {$_.Name -like "*Squirrel*" -or $_.Name -like "*Update*"}

# Result: All client files dated July 19, no update activity

Network Infrastructure Analysis:
Real-time network monitoring during MCP operations revealed completely different backend infrastructures:

# Claude Desktop monitoring showed connections to:
# - 2607:6bc0::10 (Anthropic ASN 399358) 
# - 18.97.36.54 (AWS EC2)
# - 64:ff9b::2224:3967 (Google Cloud)

# VS Code monitoring showed connections to:
# - 140.82.114.21 (GitHub)
# - 51.116.246.106, 20.42.65.85 (Microsoft Azure)
# - 4.225.11.192 (AI service routing)

This definitively proves the regression is in Anthropic's own infrastructure, not client-side.

---

CURRENT WORKAROUND

For users: Start a new conversation for each MCP workflow requiring multiple tool calls.

For developers: This bug makes any multi-step MCP workflow impossible in Claude Desktop until Anthropic fixes their backend MCP processing.

---

IMPACT ASSESSMENT

Severity: CRITICAL - ESCALATING - Complete failure progression from MCP-specific to application-wide crashes

Affected Users:

  • ✅ Confirmed Cross-Subscription Impact: Both Claude Pro and Max plan subscribers experiencing identical failures
  • ✅ Cross-Platform Confirmed: Windows, macOS, and Linux (WSL Ubuntu) users with comprehensive testing validation
  • ✅ Real-time Validation: Testing during Anthropic's acknowledged service disruption
  • ✅ Claude Code CLI users: Systematic API communication failures confirmed across Windows and Linux platforms
  • Scope: ALL users of Anthropic-owned client applications routing through ASN 399358 regardless of platform or subscription tier

Unaffected Users:

  • ✅ Confirmed: VS Code Claude users (different backend infrastructure via Microsoft/GitHub)
  • Likely: Third-party Claude integrations using different API pathways

ESCALATING BUSINESS IMPACT:

  • Phase 1 (July 23): MCP functionality degraded - multi-step workflows impossible
  • Phase 2 (Current): Complete Claude Desktop application crashes after first MCP call
  • Backend JSON Processing: Systematic malformed response generation
  • Customer Experience: Forces users to rely on third-party integrations for functional Claude access
  • Service Reliability: Real-time correlation with official service disruption acknowledgments

Incident Timeline:

  • July 23, 2025: Initial Anthropic backend infrastructure regression
  • Ongoing: Escalating severity with complete application failures and official service disruption acknowledgments

DEFINITIVE CONCLUSION: This represents a comprehensive infrastructure failure affecting Anthropic's entire client ecosystem, with escalating severity requiring immediate intervention.

---

URGENT RECOMMENDATION FOR ANTHROPIC TEAM:

This analysis provides definitive evidence of a CRITICAL ESCALATING INFRASTRUCTURE FAILURE in Anthropic's own backend infrastructure (ASN 399358).

IMMEDIATE PRIORITY ACTIONS REQUIRED:

  1. EMERGENCY INFRASTRUCTURE REVIEW - IMMEDIATE - Complete audit of ASN 399358 infrastructure changes deployed July 23, 2025
  2. JSON Response Generation Fix - CRITICAL - Address systematic malformed JSON response generation causing client crashes
  3. MCP Protocol Layer Repair - HIGH - Fix conversation state corruption causing missing arguments object
  4. Cross-Subscription Impact Assessment - HIGH - Validate impact across all subscription tiers (confirmed Pro and Max affected)
  5. Application Stability Restoration - CRITICAL - Prevent complete client application crashes

DEFINITIVE EVIDENCE SUMMARY:

  • ✅ Cross-Subscription Validation: Both Pro and Max plan users experiencing identical failures with matching technical log patterns
  • ✅ Cross-Platform Validation: Windows, macOS, and Linux (WSL Ubuntu) comprehensive testing confirms universal impact
  • ✅ Real-time Service Correlation: Testing during official "temporary service disruption"
  • ✅ Network Infrastructure Isolation: Only ASN 399358 clients affected, VS Code (Microsoft/GitHub) functional
  • ✅ Escalating Severity: Progression from MCP failures to complete application crashes
  • ✅ JSON Processing Corruption: Backend generating malformed responses
  • ✅ API Communication Failures: Claude Code CLI systematically broken across multiple platforms
  • ✅ Technical Log Evidence: Client logs demonstrate exact pattern of first call success with arguments object, subsequent calls fail across subscription tiers

ROOT CAUSE LOCATION CONFIRMED:
Backend infrastructure regression in Anthropic's own infrastructure (ASN 399358) deployed July 23, 2025. The fact that:

  • Both Claude Desktop (MCP failures → application crashes) and Claude Code CLI (complete API failures) are affected
  • Cross-subscription tier validation (Pro and Max plans)
  • Real-time correlation with official service disruption acknowledgments
  • VS Code Claude (Microsoft/GitHub infrastructure) remains functional

Provides conclusive evidence of a comprehensive infrastructure failure requiring immediate emergency intervention rather than application-specific debugging.

BUSINESS CONTINUITY IMPACT: This represents a complete degradation of Anthropic's primary client ecosystem, forcing customers to rely on third-party integrations for functional Claude access.

reverie · 1 year ago

This sounds like an issue with Desktop Commander MCP, which we unfortunately can't help with.

DannyJanmaat · 1 year ago
This sounds like an issue with Desktop Commander MCP, which we unfortunately can't help with.

With respect, this response demonstrates a fundamental misunderstanding of the technical evidence.
This is definitively NOT a Desktop Commander MCP issue. Our comprehensive analysis proves this is an Anthropic backend infrastructure regression affecting ALL MCP servers universally.
Key Evidence:
🔍 Multiple MCP Server Validation:

Desktop Commander ❌ (fails after 1st call)
Windows-MCP ❌ (fails after 1st call)
Custom Rust MCP implementations ❌ (identical pattern)
File server MCP ❌ (same failure)

🔍 Control Group Proof:

Same exact MCP servers work perfectly in VS Code Claude
This definitively proves MCP servers are not the problem

🔍 Network Infrastructure Analysis:

Issue affects only clients routing through Anthropic ASN 399358
VS Code Claude (Microsoft/GitHub infrastructure) remains functional
This isolates the problem to Anthropic's own backend

🔍 Technical Root Cause:

Client logs show Anthropic's backend stops generating "arguments" object after first successful MCP call
Pattern is 100% reproducible across all MCP servers
Cross-platform (Windows, macOS, Linux) validation
Cross-subscription tier (Pro, Max) confirmation

🔍 Timeline Correlation:

Regression introduced July 23, 2025
Real-time correlation with Anthropic's acknowledged "service disruption"

The evidence unequivocally shows this is an Anthropic backend infrastructure issue, not an MCP server problem. Desktop Commander is simply one of many affected servers demonstrating the same backend-generated malformed requests.
This requires Anthropic infrastructure team intervention, not MCP server debugging.

nichecode · 1 year ago

@reverie ☝️. I am experiencing the same issue with my own mcp tool that uses stdio. First call works then subsequent calls fail. Too much of a coincidence to just be desktop commander.

github-actions[bot] · 1 year ago

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.

Related Claude Code issues

Matched on shared title terms, labels, topic and reported release — ranked so issues with real discussion come first.

Browse by topic

Same class of failure, ranked by community engagement — this issue is one of many, so it may not appear in the visible list: MCP server connection issues

Browse all Claude Code issue topics →