Skip to main content

Quickstart for Claude Desktop

Claude Desktop connects to your Files.com site through the Files.com MCP Server. The Remote MCP Server is the recommended path for site operations and supports browser sign-in without installing a local server. The Local MCP Server runs on your computer and includes tools to upload files from it and save downloads there. The Remote and Local comparison explains which fits your work.

For a new connection, use the matching setup below. If Claude already connects to Files.com, follow Switching Between Remote and Local.

Install Claude Desktop

Download the Claude Desktop appExternal LinkThis link leads to an external website and will open in a new tab 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/

Sign In with Files.com

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, open Customize > Connectors and add a custom connector with your Files.com MCP endpoint. Choose browser sign-in and complete the Files.com login and approval. Claude manages the connection through your Claude account; it is separate from entries in claude_desktop_config.json. Anthropic's custom connector instructionsExternal LinkThis link leads to an external website and will open in a new tab cover adding and removing these connectors.

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

API Key

Use API Key authentication when you need the key's access restrictions or a fixed credential. You will need a Files.com API Key.

The configuration below uses mcp-remote, a bridge that runs on your computer and connects to Files.com's hosted server. This is a Remote MCP connection, even though the bridge runs locally; it does not run the Files.com Local MCP Server's Python package.

Install Node.js

The mcp-remote configuration uses npx, which is included with Node.js. Download and install Node.jsExternal LinkThis link leads to an external website and will open in a new tab 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 DesktopExternal LinkThis link leads to an external website and will open in a new tab 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 My Files.com Site entry below under the existing mcpServers object, preserving other server entries and settings. If you are creating the file, use the complete example. Replace 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 Python 3.11 or newerExternal LinkThis link leads to an external website and will open in a new tab for your operating system. The configuration below selects Python 3.11 or newer for the local package.

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 instructionsExternal LinkThis link leads to an external website and will open in a new tab 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 uvxExternal LinkThis link leads to an external website and will open in a new tab. 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 DesktopExternal LinkThis link leads to an external website and will open in a new tab 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

Add the Files.com entry below under the existing mcpServers object, preserving other server entries and settings. If you are creating the file, use the complete example.

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": [
        "--python",
        ">=3.11",
        "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.

Switching Between Remote and Local

Claude Desktop can keep both Files.com connections configured. Give them distinct names, such as Files.com Local and Files.com Remote, so you can identify the connection and its credentials. In a conversation's Connectors menu, enable the connection you intend to use and disable the other when both reach the same site. This avoids giving Claude two sets of similar tools with potentially different permissions.

The examples above use Files.com for Local and My Files.com Site for Remote. These are display names. Identify a configuration entry by its command and arguments: Local launches files-com-mcp, while the Remote configuration-file example launches mcp-remote with your site's URL. Keep all entries inside one mcpServers object with a unique name for each entry.

From Local to Remote

You can add and test the Remote connection before removing Local. The Python package can remain installed throughout the switch.

  1. Add the Remote connection using Sign In with Files.com, or use the Remote API Key configuration if you need to retain API-key restrictions. For browser sign-in, choose the Files.com account whose permissions Claude needs. The old key's restrictions do not carry over to the login session.
  2. Start a new conversation and enable only the Remote Files.com connection. Ask Claude to list a folder that the account or key is allowed to access. Check that it returns the expected Files.com contents; seeing a connector or tool list alone does not verify authentication.
  3. To retire Local, remove its entire entry from claude_desktop_config.json, including its command, args, and env. Preserve other entries, keep the JSON valid, then fully quit and reopen Claude Desktop. If you want to keep Local for future transfers, leave its entry in place and disable it in conversations that use Remote.
  4. After switching to browser sign-in, revoke the old API key if it was dedicated to the retired Local connection. Removing its configuration does not revoke it. If the key is shared, move the other integrations to replacement credentials first. Keep it while any retained Local or Remote connection still uses it.

Uninstalling the local package is optional. Remove it only when no other client needs that installation. Removing the connection or package does not delete your Files.com files.

From Remote to Local

Local requires an API key, even if you previously used Sign In with Files.com. Choose a dedicated key with the permissions needed for the local work.

  1. Complete the Local MCP setup, including the local transfer directory if needed. Add the Local entry alongside any existing servers, then fully quit and reopen Claude Desktop.
  2. Start a new conversation and enable only the Local Files.com connection. Ask Claude to list an allowed Files.com folder. If you are switching for local transfers, also test an upload or download with a sample file in your configured local directory.
  3. To retire a browser-authenticated Remote connector, remove it from Customize > Connectors. To retire the Remote API-key bridge shown above, remove its mcp-remote entry from claude_desktop_config.json and fully quit and reopen Claude Desktop. You can instead retain Remote and disable it in conversations that use Local.

Removing a connector changes Claude's configuration. For ending access at Files.com, use the session and credential controls. Delete a retired Remote API key only after confirming that no retained connection or integration uses it.

Debugging

Claude Desktop provides debugging informationExternal LinkThis link leads to an external website and will open in a new tab to help you troubleshoot issues and verify connectivity with its AI and any connected MCP tools.