File not found when starting radon-mcp

[tharakadesilva]

Description

When I run the following command:

npx -y radon-mcp@latest

I am running into:

Using workspace: /Users/tharakadesilva/git_tree/tharakadesilva/my-monorepo/apps/my-app
Starting MCP Proxy Server...
MCP Proxy Server started successfully
✗ Connection attempt failed: Error: Failed to read Radon config from /Users/tharakadesilva/Library/Caches/com.swmansion.radon-ide/Mcp/radon-mcp-1ea7080dc07d44a1b292971d4efa6aa0.json: Error: ENOENT: no such file or directory, open '/Users/tharakadesilva/Library/Caches/com.swmansion.radon-ide/Mcp/radon-mcp-1ea7080dc07d44a1b292971d4efa6aa0.json'
Retrying in 5 seconds...

Environment

• Version of currently used Radon IDE (Extensions tab -> click on Radon IDE extension -> version is located next to the extension name): 2.1.2
• Version of React Native/Expo used in the project

  npmPackages:
    @expo/fingerprint: catalog: => 0.16.5 
    @expo/metro-runtime: catalog: => 55.0.6 
    @expo/vector-icons: catalog: => 15.1.1 
    @react-navigation/bottom-tabs: catalog: => 7.15.5 
    @react-navigation/drawer: catalog: => 7.9.4 
    @react-navigation/elements: catalog: => 2.9.10 
    @react-navigation/native: catalog: => 7.1.33 
    @sentry/cli: catalog: => 3.3.0 
    @sentry/react-native: catalog: => 7.11.0 
    @tamagui/babel-plugin: catalog: => 2.0.0-rc.22 
    @tamagui/cli: catalog: => 2.0.0-rc.22 
    @tamagui/metro-plugin: catalog: => 2.0.0-rc.22 
    @types/jest: catalog: => 29.5.14 
    @types/node: catalog: => 25.3.5 
    @types/react: catalog: => 19.2.14 
    babel-preset-expo: catalog: => 55.0.10 
    eas-build-cache-provider: catalog: => 18.0.2 
    expo: catalog: => 55.0.5 
    expo-application: catalog: => 55.0.8 
    expo-calendar: catalog: => 55.0.9 
    expo-clipboard: catalog: => 55.0.8 
    expo-constants: catalog: => 55.0.7 
    expo-crypto: catalog: => 55.0.9 
    expo-dev-client: catalog: => 55.0.11 
    expo-device: catalog: => 55.0.9 
    expo-font: catalog: => 55.0.4 
    expo-glass-effect: catalog: => 55.0.7 
    expo-haptics: catalog: => 55.0.8 
    expo-image: catalog: => 55.0.6 
    expo-image-picker: catalog: => 55.0.11 
    expo-insights: catalog: => 55.0.10 
    expo-linking: catalog: => 55.0.7 
    expo-localization: catalog: => 55.0.8 
    expo-network: catalog: => 55.0.8 
    expo-notifications: catalog: => 55.0.11 
    expo-router: catalog: => 55.0.3 
    expo-secure-store: catalog: => 55.0.8 
    expo-splash-screen: catalog: => 55.0.10 
    expo-status-bar: catalog: => 55.0.4 
    expo-symbols: catalog: => 55.0.5 
    expo-system-ui: catalog: => 55.0.9 
    expo-updates: catalog: => 55.0.12 
    expo-web-browser: catalog: => 55.0.9 
    jest: catalog: => 29.7.0 
    jest-expo: catalog: => 55.0.9 
    react: catalog: => 19.2.0 
    react-dom: catalog: => 19.2.0 
    react-native: catalog: => 0.83.2 
    react-native-gesture-handler: catalog: => 2.30.0 
    react-native-reanimated: catalog: => 4.2.1 
    react-native-safe-area-context: catalog: => 5.6.2 
    react-native-screens: catalog: => 4.23.0 
    react-native-svg: catalog: => 15.15.3 
    react-native-web: catalog: => 0.21.2 
    react-native-worklets: catalog: => 0.7.2 
    tamagui: catalog: => 2.0.0-rc.22 
    typescript: catalog: => 5.9.3 

[tharakadesilva]

I tasked an AI to try find the issue. It ended up at:

function shouldUseDirectRegistering() {
  if (import_vscode73.version.includes("1.109.")) {
    return false;
  }
  return import_vscode73.version.localeCompare("1.105.0", void 0, { numeric: true }) >= 0 && getEditorType() === "vscode" /* VSCODE */;
}

My VSC version is Version: 1.111.0. I think this forces folks on VSC to use the built-in tools for Radon AI and doesn't start the local MCP server.

I am trying to use it in a different harness (in OpenCode).

[tharakadesilva]

That was definitely it! I patched it locally like this and it worked as expected:

diff --git i/dist/extension.js w/dist/extension.js
index 0eb996c..b442af8 100644
--- i/dist/extension.js
+++ w/dist/extension.js
@@ -484051,12 +484051,10 @@ var RadonMcpController = class _RadonMcpController {
       }
       const radonAiEnabled = isAiEnabledInSettings() && this.radonAvailabilityStatus === "AVAILABLE" /* AVAILABLE */;
       setGlobalEnableAI(radonAiEnabled);
-      if (!shouldUseDirectRegistering()) {
-        if (radonAiEnabled) {
-          this.enableServer();
-        } else {
-          this.disableServer();
-        }
+      if (radonAiEnabled) {
+        this.enableServer();
+      } else {
+        this.disableServer();
       }
     };
     this.radonAvailabilityStatus = options.radonAvailabilityStatus;

[latekvo]

Hi, thanks for reporting this. Just fixed this issue, it should be available in the next nightly release (if all the tests pass), and certainly in the next proper release.