Files.com integrationFiles.com logo

Files.com integration for AI agents.

Files.com integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Files.com tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

What your agents can do

Real Files.com actions, managed and audited.

Your user connects Files.com once; your agent can then files.com moves and manages every file your business depends on — across any cloud and any partner, from one place. It replaces MFT tools, SFTP servers, file servers, and scripts — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

  1. 1

    Your user grants Files.com access once (OAuth) — the token lands in the vault.

  2. 2

    Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.

  3. 3

    Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Files.com tools.

0 tools are generated from the published Files.com catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.

No tools match “”.

FAQ

Files.com integration, answered

How do AI agents use Files.com through Open Connector?
Your user connects Files.com once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Files.com tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Files.com MCP server?
Yes. Open Connector can serve Files.com as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Files.com actions with credentials injected server-side.
Where do Files.com credentials live?
In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Files.com — keep the keys.

Open source, self-hostable, with Files.com credentials that never leave your infrastructure. Run it from source today.