MCP Access Permissions
The actions the AI can perform depend on the authenticated account or API key. Each available MCP tool runs within those permissions.
Sign In with Files.com
When you authenticate via Sign In with Files.com, the MCP Server receives a bearer token representing your Files.com login session. The AI uses the permissions of that Files.com user.
Logging in as a site administrator gives the AI administrator access. Logging in as a regular user limits the AI to the actions and folder permissions assigned to that account.
Each sign-in is scoped to your Files.com site and tied to the user who authenticated. Sites with AI features disabled cannot complete sign-in.
API Key
The AI's access is limited by the API key's permission and Workspace scopes and, for a user key, its associated user account.
Use a Files Only key for a client that only needs to work with files and folders. This scope prevents administrative actions even when the key belongs to a Site Administrator. Add a path restriction when the work should stay within one folder and its subfolders.
A Full Access user key permits the operations available to its associated user, including administrative actions when that user can perform them. A Full Access site-wide key has Site Administrator access within its Workspace scope.
Re-authentication
Remote MCP Server tool calls are exempt from re-authentication. Selected account and credential changes proceed without an additional password or 2FA confirmation. This applies to every operation covered by that control, whether the login session was obtained through Sign In with Files.com or created through the REST API.
API-key authentication is also exempt from re-authentication, on both the Remote and Local MCP Servers. Files.com still checks permissions for each operation. Choose access for the actions you trust the AI to perform.