A remote connector for your files
Give a compatible MCP client tools for working with your cloud files. Files for AI provides project-scoped access for discovery, reading, downloads and versioned writes through a remote endpoint.
Original files. Project permissions. Access you control.
BUILT AROUND YOUR FILES
Sign in and approve specific projects and read or write access. Requests are checked against current membership and connection permissions. A Viewer can authorize their own read-only connection without becoming a project administrator.
Clients can list files, search names and supported extracted text, inspect metadata, and read bounded text excerpts. Responses identify the version used and report when content is unsupported or a result is truncated.
An agent with HTTP access can upload binary files through signed multipart URLs. A web assistant can submit generated UTF-8 text through the bounded write_file tool. Both paths use the same project permissions and file verification.
File metadata includes stable file IDs, immutable version IDs and raw SHA-256 hashes. An update must identify the version it expects to replace, so another user's newer revision produces a conflict rather than a silent overwrite.
HOW IT WORKS
Configure your compatible MCP client with the Files for AI server address for your workspace. A hosted connection uses HTTPS and the remote Streamable HTTP transport.
Complete sign-in and review the requesting client. Grant read-only access for retrieval, or read/write access when the assistant should be allowed to save files.
Ask the assistant to find a file and inspect the relevant version. For an upload or generated file, check its verification status before treating the new revision as ready.
CAPABILITIES & LIMITS
Storing an original file and reading its contents are different capabilities. Here’s what to expect.
Client support varies. Connector-directory availability and support for a specific assistant should be checked separately.
The remote connector accesses authorized cloud files. It does not grant access to local folders on your computer.
A FEW PRACTICAL ANSWERS
MCP gives compatible assistants a common way to discover and call file tools. Files for AI supplies the storage, project permissions and version checks behind those tools. The client still needs to support the remote transport and authorization flow.
Only if that client exposes the attachment's bytes and can perform the required HTTP upload. A signed URL does not transfer an attachment by itself. Use the web upload flow when those capabilities are unavailable, or write_file for generated text within its size limit.
It can compare the cloud version's verified SHA-256 with a hash it computes from another file. Matching hashes establish byte equality. They do not establish permission, create a persistent link, or authorize automatic updates.
Subsequent connector requests lose access. A storage URL issued before revocation can remain usable until its short expiry, so revoking a connection does not promise immediate invalidation of every previously issued download URL.
FILES FOR AI
Bring your files together and choose how your assistants can use them.