Claude Desktop connects to your Files.com site through the Files.com MCP Server. You have two options. The Remote MCP Server requires no software installation and is the recommended path for most users. The Local MCP Server installs and runs on your own machine. Follow the section that matches your setup.

Install Claude Desktop

Download the Claude Desktop app and install it.

Claude Desktop is available for Windows and Mac.

Connecting via the Remote MCP Server

The Remote MCP Server runs on your Files.com site. You can connect to multiple Files.com sites simultaneously by adding an entry for each site in your configuration.

To find your Remote MCP Server URL, substitute your Files.com subdomain or custom domain into the appropriate format:

https://<mysite>.files.com/api/ai/mcp/v1/

https://<mycustomdomain>/api/ai/mcp/v1/

This method opens a browser window to log in to your Files.com account. No API key is required. If your Files.com site uses single sign-on (SSO), the browser sign-in redirects to your identity provider as normal.

In Claude Desktop, use the application's settings to add your Files.com MCP endpoint as a custom connector. On the first connection, a browser window opens to complete sign-in. Claude Desktop caches the session and connects automatically on subsequent restarts.

Note that on corporate Claude accounts, your organization may have disabled the ability to add custom connectors.

API Key

Use this method if you need a fixed credential for an automated or headless workflow. You will need a Files.com API Key.

Install Node.js

Claude Desktop uses npx to connect to the Remote MCP Server. npx is included with Node.js. Download and install Node.js for your operating system.

Make sure that npx is working correctly prior to proceeding. Use the following command from a terminal window to verify that npx is working:

npx --version

Update the configuration file for Claude Desktop to point at the Files.com MCP Server.

The configuration file can be found at:

Windows: %APPDATA%\Claude\claude_desktop_config.json
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

Add the following to your configuration file, replacing YOUR_API_KEY with your Files.com API Key and the URL with your site's Remote MCP Server URL:

{
  "mcpServers": {
    "My Files.com Site": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mysite.files.com/api/ai/mcp/v1/",
        "--transport",
        "http-only",
        "--header",
        "X-FilesAPI-Key: YOUR_API_KEY",
        "--no-auth"
      ]
    }
  }
}

Make sure that the JSON contained in the configuration file is valid and has no syntax errors. Claude Desktop will not register an MCP server if its configuration file is corrupt or invalid.

Save the file and restart Claude Desktop. Files.com will appear as an available connector in Claude Desktop.

Connecting via the Local MCP Server

Claude Desktop launches the local Python package on the same machine and communicates through standard input and output (STDIO). The package is for local use only. For a network connection, use the Remote MCP Server.

Local setup requires Python, the uv package manager, and a Files.com API Key.

Install Python

Download and install the Python programming language for your operating system.

Install uv

Install the uv Python package and project manager. This manager is recommended for running Python based MCP servers with Claude.

Follow the official installation instructions for your operating system.

Make sure that uv is working correctly prior to proceeding. Use the following command from a terminal window to verify that uv is working:

uv --version

Install Files.com MCP Server

The configuration below launches files-com-mcp with uvx. On first launch, uvx downloads the package into an isolated environment and runs it. You do not need a separate uv venv or pip install step for this setup.

Configure Claude Desktop for the Local MCP Server

Update the configuration file for Claude Desktop to point at the local MCP Server.

The configuration file can be found at:

Windows: %APPDATA%\Claude\claude_desktop_config.json
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

The example below includes the optional FILES_COM_LOCAL_ROOT setting to restrict local uploads and downloads to one directory and its subdirectories. Create or choose a directory for these transfers before starting the server.

Replace YOUR_API_KEY with your Files.com API Key and C:\\FilesMCP with that directory's absolute path. Windows paths need doubled backslashes in JSON, as shown. On Mac, use a path such as /Users/yourname/FilesMCP, with your actual account name.

{
  "mcpServers": {
    "Files.com": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "files-com-mcp"
      ],
      "env": {
        "FILES_COM_API_KEY": "YOUR_API_KEY",
        "FILES_COM_LOCAL_ROOT": "C:\\FilesMCP"
      }
    }
  }
}

Make sure that the JSON contained in the configuration file is valid and has no syntax errors. Claude Desktop will not register an MCP server if its configuration file is corrupt or invalid.

Save the file and restart Claude Desktop. Files.com will appear as an available connector in Claude Desktop.

FILES_COM_LOCAL_ROOT applies to local transfer paths; your API key still determines access to Files.com. Omitting the setting or leaving it empty permits any local path the server's operating-system account can access. An invalid nonempty value prevents startup. The local directory path rules explain relative paths and symbolic links. Changes to the setting take effect when Claude Desktop restarts the server.

Debugging

Claude Desktop provides debugging information to help you troubleshoot issues and verify connectivity with its AI and any connected MCP tools.

Quickstart for Claude Desktop