Skip to main content

Let AI Agents Operate Your Site Through MCP

Files.com runs a hosted MCP server, built on the open Model Context Protocol standard. An AI client like Claude Desktop or Cursor can upload files, manage users, read logs, and run operations against a live Files.com site. The AI works under the same API-key authentication, folder permissions, and audit trail as any other client. There’s no new access model to reason about, so you can turn it on without rethinking how your site is secured.

AI Agents, Treated Like Any Other Client

An MCP server hands an AI client a set of actions it can take on your behalf. MCP calls these actions “tools.” 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, so it can never reach a folder you didn’t grant. Every move it makes lands in your audit log.

An MCP client connected to Files.com: the AI calling Files.com tools to list, move, and manage files against a live site through the Model Context Protocol

Two Ways To Run It

Both modes give you the same tools and the same API-key login. Pick the one that fits your network and your compliance rules.

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. You skip the setup entirely, so this is the fastest way to connect and the recommended default.

Local Server, Runs In Your Infrastructure

A Python package you install and run yourself. This is 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, so nothing leaves your network.

What An AI Can Do Through It

The tools map onto the operations your team already runs through the API. The AI does the same work, under the same controls.

Move And Find Files

Upload, download, find, copy, move, delete, and list files, and create folders. These are the everyday file operations an agent needs to do real work, not just look around.

Manage Share Links

Create, list, find, update, and delete share links, including recipients, registrations, and notifications. The AI can hand a file to someone outside your team on your behalf, without you cutting the link by hand.

Administer Users And Access

User management, group management, and folder-permission management. An admin can let the AI handle routine account and access work, which is the busywork that fills a ticket queue.

Read The Logs

Action logs, API request logs, FTP, SFTP, and WebDAV logs, automation and sync logs, login history, and settings-change logs. The AI can investigate what happened, not just make changes.

Where MCP Fits In The Bigger AI Picture

MCP is one of four ways AI works with Files.com. Here, the intelligence lives in your AI client, and 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.

See The Full AI Story

MCP Server Questions

What teams ask about connecting AI clients, authentication, permission scoping, auditing, and the available tool surface.

Connect Your AI Client To Files.com

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