Files.fm API and Read-Only MCP Access for Developers and Coding Agents

Over recent weeks, Files.fm has expanded its public API documentation and released the first version of a hosted Model Context Protocol (MCP) connector. Together, these updates make Files.fm cloud storage easier to integrate into applications, business workflows, automation tools, and AI-assisted development environments.

The updated documentation brings the recommended REST API V2, compatible V1 endpoints, a machine-readable OpenAPI specification, and MCP guidance into one reference. It is written for both human developers and software or coding agents that need an accurate description of Files.fm capabilities.

What can the Files.fm API be used for?

The Files.fm REST API allows authorized applications to work with cloud files and folders programmatically. Depending on the endpoint and account permissions, integrations can:

• create folders and upload files from business systems or automated workflows;
• list folder contents and retrieve file or folder metadata;
• download files for processing, delivery, backup, or synchronization;
• rename, move, delete, and restore content;
• connect file sharing, previews, conversion, e-signature, or document workflows; and
• build customer portals, upload forms, media pipelines, archives, and internal integrations around Files.fm storage.

API V2 is recommended for new integrations where an equivalent endpoint exists. Documented V1 endpoints remain available for compatibility and for functions that do not yet have a V2 equivalent.

Documentation for humans and machines

The Files.fm API documentation brings the API references together in one place. Developers can use the OpenAPI specification with code generators, API clients, testing tools, and automation platforms. Swagger UI provides an interactive way to explore the contract, while the Markdown references are convenient for developers and language models.

This structure is particularly useful during implementation. A developer can review request parameters and response fields, while a coding agent can search the same source material before generating an integration, tests, or data-mapping code. This reduces guesswork and helps keep generated code aligned with the current API contract.

Read-only MCP access for coding agents

The hosted Files.fm MCP endpoint is available at https://api.files.fm/api/mcp. MCP provides a standardized way for compatible AI clients and coding agents to discover tools and resources instead of relying only on manually copied prompts or custom integration code.

With the current read-only connector, an authenticated agent can:

• locate files and folders visible to the Files.fm account;
• browse folder contents and inspect metadata;
• search file names and available indexed metadata;
• read permitted files within documented size and format limits; and
• search the Files.fm API documentation.

This can support practical workflows such as finding project specifications, reading technical documentation, locating reports, summarizing text files, comparing stored materials, or helping a developer write code against the Files.fm API. Public API-documentation search is available without access to private account files.

Read-only by design

The first MCP version deliberately does not upload, rename, move, delete, restore, share, or otherwise change files. Private tools require a Files.fm API token, and results continue to follow existing account file and folder permissions. Rate limits and bounded file reads help keep automated use predictable.

Write operations remain available through the REST API, where applications can apply explicit validation, authorization, confirmation, and error handling. This separation lets coding agents inspect context safely while developers retain clear control over changes.

Getting started

Developers can create and revoke API tokens in Files.fm account settings, connect a compatible MCP client to the hosted endpoint, or use the REST and OpenAPI documentation to build a direct integration. Production automations should use HTTPS, keep tokens out of source code and URLs, and use dedicated, limited-access accounts or tokens where practical.

The read-only MCP connector is a first step toward deeper agent-oriented Files.fm workflows. We will continue improving the API, documentation, and carefully controlled automation capabilities based on real integration needs and user feedback.