Skip to main content

Troubleshooting MCP

Most MCP issues fall into two categories: a configuration file the client cannot parse, or a startup failure where the client cannot launch the MCP server. The sections below cover both. For client-specific behavior, also refer to the documentation for the MCP clientExternal LinkThis link leads to an external website and will open in a new tab you are using with the Files.com MCP Server.

Configuration Issues

Your MCP client will not register an MCP server if its configuration file is corrupt or invalid.

For clients that use the Claude Desktop JSON configuration fileExternal LinkThis link leads to an external website and will open in a new tab method, make sure that the JSON contained in the configuration file is valid and has no syntax errors.

Startup Errors

Startup errors occur when the MCP client cannot run the MCP server.

Errors such as spawn uvx ENOENT and Could not connect to MCP server Files.com indicate startup issues.

uvx Errors

The spawn uvx ENOENT error indicates that the uvx command cannot be found on the system PATH environment variable.

Make sure that uv is installedExternal LinkThis link leads to an external website and will open in a new tab on your system.

If the uvx command is not installed in a system PATH location, then update the MCP client JSON configuration file to specify the full path to the uvx command.

For example, in the configuration file, change:

  "command": "uvx",

to:

  "command": "C:\path\to\local\bin\uvx",

You can find the location of the uvx command using the following commands from a terminal window:

On Windows, run where uvx. On Mac, run which uvx.

npx Errors

The spawn npx ENOENT error indicates that the npx command cannot be found on the system PATH. npx is included with Node.js. Make sure Node.js is installedExternal LinkThis link leads to an external website and will open in a new tab on your system.

If npx is installed but not in a system PATH location, update the configuration file to specify the full path to the npx command.

For example, change:

  "command": "npx",

to:

  "command": "C:\path\to\local\bin\npx",

You can find the location of the npx command using the following commands from a terminal window:

On Windows, run where npx. On Mac, run which npx.