Remote Server — Nothing To Install
Files.com hosts and runs the MCP server for you at a URL on your own site. Point your AI client at it, paste in an API key, and it works. This is the fastest way to connect, and the recommended default.
An MCP server hands an AI client a set of actions — “tools” in MCP terms — that it can use on your behalf. Files.com turns the platform into tools the AI can call, so a request like “move yesterday’s vendor feeds into the archive folder, then summarize what arrived” becomes a real operation on your site.
This is safe to turn on because the MCP server is not a new permission system. It runs on top of the same API and logins your scripts and SDKs already use. The AI can only do what its API key’s user account is allowed to do, and every move it makes lands in your audit log.
Both modes give you the same tools and the same API-key login. Pick the one that fits your network and compliance rules.
Files.com hosts and runs the MCP server for you at a URL on your own site. Point your AI client at it, paste in an API key, and it works. This is the fastest way to connect, and the recommended default.
A Python package you install and run yourself, for teams that need to run it on-premise or that block outbound connections to hosted services. It gives you the same tools and the same API-key login as the remote server.
A broad and growing set of tools, mapped onto the operations your team already performs through the API.
Upload, download, find, copy, move, delete, and list files, and create folders — the everyday file operations an agent needs to actually do work, not just look around.
Create, list, find, update, and delete share links, including recipients, registrations, and notifications — so an AI can hand a file to someone outside your team on your behalf.
User management, group management, and folder-permission management, so an admin can let the AI handle routine account and access work.
Action logs, API request logs, FTP, SFTP, and WebDAV logs, automation and sync logs, login history, and settings-change logs — so an AI can investigate what happened, not just make changes.
MCP is one of four ways AI works with Files.com. Here, the intelligence lives in your AI client — Files.com is the system being operated. That sits alongside the built-in AI Assistant, agents that drive the API directly, and AI running inside your workflows.
The MCP server ships across all plans. SIEM-exported audit logs and audit-log retention scale by plan, so confirm what your tier includes on the pricing page.
What teams ask about connecting AI clients, authentication, permission scoping, auditing, and the available tool surface.
Start a free trial, generate a least-privilege API key, and point Claude Desktop, Cursor, or any MCP client at your site. Every action runs under the permissions you set and lands in your audit log.
No credit card required • Free for 7 days • Live in minutes