Files.com
Manage files, users, groups, permissions, and secure file sharing through Files.com's hosted MCP server
About
Securely manage Files.com resources and perform file operations through Files.com’s hosted MCP server, without running a local server.
See Files.com’s official MCP server documentation for setup instructions, authentication options, and current capabilities.
Features
- File & Folder Operations: Find, copy, move, delete, list, zip, and unzip files and folders
- User and Group Management: Create, update, list, and delete users and groups
- Share Link Management: Create and manage secure file sharing links, recipients, registrations, and notifications
- Permission Management: Manage folder-level permissions for users and groups
- History & Audit Logging: Inspect file activity, logins, API requests, transfers, automations, and settings changes
- Automation and Remote Servers: Inspect automation workflows and remote server connections
What you’ll need to connect
Enter your Files.com site subdomain. For example, enter acme if your site is available at https://acme.files.com.
Obot constructs the MCP endpoint as https://<your-site>.files.com/api/ai/mcp/v1/.
Sign in with your Files.com account when prompted. OAuth authentication follows your existing Files.com user permissions and supports SSO. Your site’s AI features must be enabled, and a Files.com Site Administrator must enable MCP Dynamic Client Registration under AI > Settings at https://<your-site>.files.com/ui/aiFeatures/settings.
For automated or headless use, you can provide a Files.com API key instead of signing in. The key inherits the permissions of its associated Files.com user.
Custom domains are not accepted; use the site’s corresponding Files.com subdomain instead.
⚠️ Upgrade notice
If you’re upgrading this server, note that this replaces the Obot-hosted Files.com server with Files.com’s official hosted MCP server.
- Reconnect required: Provide your Files.com site subdomain and connect with either OAuth or a Files.com API key.
- OAuth setup: A site administrator must enable MCP Dynamic Client Registration.
- Compatibility: Custom domains are not accepted, tool parameters may change, and local file upload and download tools remain unavailable.
Configuration
Environment variables
| Variable | Description | Required |
|---|---|---|
FILES_COM_SITE | Your Files.com site subdomain, for example `acme` for `https://acme.files.com` | Yes |
Request headers
| Header | Description | Required |
|---|---|---|
X-FilesAPI-Key | Optional Files.com API key for automated or headless authentication | No |
Remote runtime
- Url Template
https://${FILES_COM_SITE}.files.com/api/ai/mcp/v1