Introduction

The Files.com MCP server lets an LLM client such as Claude or ChatGPT act inside your Files.com site: upload and download files, query folders and file metadata, create and manage users, and run automations. It works with the permissions of the API key you give it, and its actions are logged like those of any other API client.

What MCP Is

The Model Context Protocol (MCP) is a standard interface through which a Large Language Model calls real APIs as part of its work. An MCP server hands the model a set of tools, and each Files.com tool is an authenticated operation in your site. With the server connected, the model can:

• Transfer files between cloud and on-premises systems
• Query folders and file metadata
• Create and manage users
• Automate workflows such as archiving or sharing

Common Use Cases

Assistants for operations teams. An internal chatbot fetches or archives files on request.

Automated workflows. An agent reacts to an incoming support request, then retrieves or uploads the files the case needs.

Developer copilots. A development-focused LLM creates users, provisions folders, or reads files while debugging.

Two Ways To Run It

The server ships as the files-com-mcp Python package, which runs locally inside your LLM client; Installation covers the setup and Using With Claude is a complete example. Files.com also operates a hosted MCP server, so an agent can connect without running the package; the Files.com AI integrations documentation describes it.