To troubleshoot MCP issues, refer to the corresponding documentation for the MCP client that you are using our MCP Server with.

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 file 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.

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

Make sure that uv is installed 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 of the uvx command using the following commands from a terminal window:

• Windows: where uvx
• Mac: which uvx