JetBrains MCP in Claude Desktop: 'No working IDE endpoint available' on tools/list

5 answers

• Best answerAgentArmorHQ teamTeam4d ago

  The issue is closed as completed, but no maintainer posted an official fix in the thread; the fixes below come from other users. The log shows the proxy starts and completes the MCP initialize handshake, then the client's tools/list request gets back {"error":{"code":-32603,"message":"No working IDE endpoint available."}}. This means npx launched the proxy, but the proxy could not reach a working JetBrains IDE endpoint on the configured host/port.

  Workarounds that worked in the thread:

  1. Reinstall Node.js via nvm (macOS ARM). One user fixed it by fully removing the Homebrew Node install and reinstalling with nvm:

     • brew uninstall --ignore-dependencies node
     • brew cleanup
     • sudo rm -f /opt/homebrew/bin/node /opt/homebrew/bin/npm /opt/homebrew/bin/npx
     • sudo rm -rf /opt/homebrew/Cellar/node
     • rm -rf ~/.npm ~/.node ~/.cache/node
     • Then install Node with nvm. The user reported this made everything work.

  2. Test with a different MCP client. Another user reported the same @jetbrains/mcp-proxy server works correctly when initialized in Cursor AI, and suspected the issue was the unofficial Linux port of Claude Desktop rather than the proxy itself.

  3. Check for MCP server conflicts. One user saw the same issue and found conflicts with other MCP servers, particularly a Postgres MCP server, appeared to be involved. The thread does not give steps to resolve that conflict.

  General advice (not stated in the thread): before reinstalling anything, verify the JetBrains IDE is actually running and that IDE_PORT matches the port the IDE is listening on (63342 in the config above).

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Didn't work)

  Configured the jetbrains MCP server in Claude Desktop with command npx, args -y @jetbrains/mcp-proxy, and env HOST=127.0.0.1 and IDE_PORT=63342. The proxy initialized and connected, but the first and every subsequent tools/list call returned error -32603 'No working IDE endpoint available.'

  Source: https://github.com/JetBrains/mcp-jetbrains/issues/38 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @darkangel91 tried on GitHub (Worked)

  On macOS ARM, removed Node and npm with brew uninstall --ignore-dependencies node and brew cleanup, deleted leftover node/npm/npx binaries and /opt/homebrew/Cellar/node, cleared ~/.npm, ~/.node and ~/.cache/node, then reinstalled Node using nvm.

  Source: https://github.com/JetBrains/mcp-jetbrains/issues/38#issuecomment-2849121955 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @spont4e tried on GitHub (Worked)

  Initialized the same @jetbrains/mcp-proxy server in Cursor AI, where it worked correctly, and concluded the problem lay with the unofficial Linux port of Claude Desktop rather than the MCP server itself.

  Source: https://github.com/JetBrains/mcp-jetbrains/issues/38#issuecomment-2849351973 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What @AppsNavigator tried on GitHub (Outcome unclear)

  Reported the same issue and noted there appeared to be conflicts with other MCP servers, particularly a Postgres MCP server. No resolution steps were provided.

  Source: https://github.com/JetBrains/mcp-jetbrains/issues/38#issuecomment-2863659274 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport