Skip to main content
Support

MCP FAQ

Fix common MCP service errors including missing command environments, initialization failures, and configuration issues.

This topic describes exceptions encountered during the installation and operation of MCP services, and provides corresponding solutions and troubleshooting steps, including handling missing command environments, service initialization failures, and configuration errors.

Failed to add or install a service

1. Missing environment for the npx command

  • Error message: failed to start command: exec: "npx": executable file not found in $PATH
  • Solution: Download and install Node.js.
The Node.js version must be v18 or later, and the npm version must be v8 or later. Lower versions may cause tool call failures.
  • You can visit the Node.js official website to download and install Node.js 18 or later, or complete the installation using one of the following methods: Installation and verification steps
    • Windows
    • macOS
    1. Download and install Node.js, and use nvm-windows to manage multiple versions:
    nvm install 22.14.0  # Install the specified version
nvm use 22.14.0
    1. After installation, run the following commands in the terminal to confirm that the installation is successful.
    node -v
npx -v
    1. If the installation is successful, the terminal displays the installed Node.js version number.

2. Missing environment for the uvx command

  • Error message: failed to start command: exec: "uvx": executable file not found in $PATH
  • Solution: Install uv. uvx is a command-line tool provided by uv, used to quickly run Python scripts.
    • You can visit the Python official website to download and install Python 3.8 or later, or complete the installation using one of the following methods: Installation and verification steps
      1. Download and install uv.
      • Windows
      • macOS
      Run the following command on Windows to install uv:
      powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
      1. After installation, run the following command in the terminal to confirm that the installation is successful.
      uv --version
      1. If the installation is successful, the terminal displays the installed uv version number.

3. Failed to initialize the MCP client

  • Error message: failed to initialize MCP client: context deadline exceeded
  • Possible causes include but are not limited to:
    • Incorrect service parameter configuration: MCP service parameters may be configured incorrectly, affecting service initialization.
    • Resource pull failure: Installation may fail because resources cannot be pulled due to network issues.
    • Network security restrictions: Security components within your company may block MCP service initialization.
  • Troubleshooting steps:
1. Click Copy complete command to obtain the full command. 2. Run the command in the terminal to obtain detailed error information. 3. Analyze the error information and apply the corresponding fix. Common issue 1: Configuration error In the example above, the error information indicates that the connection failure is caused by an incorrect Redis connection URL configuration. In this case, edit the MCP service to correct the URL configuration. Common issue 2: Resource pull failure If the command fails to run due to resource pull issues, execute the following commands in the command line to add a mirror source, then restart the Qoder CN process and try again.
  • Windows
  • macOS
npm config set registry https://registry.npmmirror.com
Common issue 3: Node.js execution blocked by security components Authorize or whitelist the Node.js process or related executable files according to the messages from the security components.

Tool usage issues

If you encounter issues using services in the MCP marketplace, contact ModelScope for technical support.ModelScope Developer Group (DingTalk group number: 44837352)

1. Tool execution fails due to incorrect environment variables or parameters

  • Troubleshooting steps:
If an MCP tool call encounters an exception or returns unexpected results, we recommend that you first expand the tool call details and view the specific error information for analysis and troubleshooting. For some MCP services (such as Mastergo and Figma), key authentication information such as API_KEY or TOKEN is included in the arguments (args).
Therefore, after installation from the MCP marketplace, you still need to manually configure these parameters.
  • Solution:
  1. Go to the My Services page.
  2. Find the corresponding MCP service and click Edit.
  3. In the service configuration, view the arguments (args) section.
  4. Replace the variable content that needs to be updated or filled in to ensure accuracy, then reconnect the service and try calling it again.

2. LLMs cannot call MCP tools

  • Confirm that you are in Agent mode.
    If no project directory is opened, the system enters only Ask mode and cannot call MCP tools. Load the corresponding project directory and switch to Agent mode.
  • Confirm that the MCP service is in a connected state:
If the service connection is interrupted, click the icon on the right side of the interface. The system automatically attempts to restart the MCP service.
  • Usage suggestion: Avoid using similar naming for MCP services and their tools (for example, TextAnalyzer-Pro and TextAnalyzer-Plus both contain a tool named fetchText with similar functionality), to prevent ambiguity when the model calls tools.

3. Personal settings and MCP tools pages cannot be opened, and the session panel is blank

When the page is blank and idea.log contains an error message such as "WARN - #c.i.u.j.JBCefApp - JCefAppConfig.class is not from a JBR module": Cause: Android Studio default settings do not support JCEF, causing personal settings, MCP, and other pages to fail to load. Solution:
  1. Configure JCEF: In the IDE, select Help > Find Action.., and in the input box that appears, type "Registry" and open it.


    Enable the option ide.browser.jcef.enabled.


    Disable the option ide.browser.jcef.sandbox.enable.
  1. Configure the IDE Runtime: Select Help > Find Action.. again, type "Choose Boot Runtime for the IDE" in the input box and open it. Select a newer JCEF Runtime version, and then click OK.
  2. Restart the IDE.

4. MCP service list cannot be loaded

The service list continues to display Loading.
  • Restart the IDE.
  • If the problem persists, try manually starting the Qoder CN service:

    Windows

    Go to the directory: .lingma/bin/x.x.x/CPU_architecture_64_system/ Execute the command: 
    Lingma.exe start

    macOS

    Click the Apple icon in the upper-left corner of the computer and select "About This Mac" to check the processor model. Then, go to the corresponding directory based on the processor model.
    • M1 chip: /.lingma/bin/x.x.x/aarch64_darwin/Qoder CN
    • Intel chip: /.lingma/bin/x.x.x/x86_64_darwin/Qoder CN
    Execute the command: 
    Qoder CN start
    After the service starts successfully, click the login button again.
Overview
Guides
Tutorials
  • Coding with Qoder CN
Support
Developer Reference