Developer platform

Files.fm API

Build and automate secure file upload, storage, sharing, processing, and content management workflows using the Files.fm API and MCP.

The Files.fm API allows developers to integrate scalable ES-based cloud storage into web, mobile, desktop, and server-side applications without building and maintaining their own file storage infrastructure and heavy file processing such as video, audio, or image conversion and streaming.

View API Documentation Swagger UI OpenAPI YAML Markdown Reference

What you can build

Customer file upload portals

Secure cloud storage integrations

Large file transfer workflows

Media and photo delivery systems or mobile apps

Client folders and project file rooms

E-signature and document workflows

File preview, thumbnail, ZIP, and download tools

AI, OCR, and media-processing pipelines

SaaS products that need reliable file storage and sharing

Main API capabilities

Upload, download, rename, move, delete, and restore files
Create, rename, move, delete, and restore folders
Retrieve file and folder metadata
Generate secure direct download and sharing links
Create ZIP archives and torrent files
Use image thumbnails and video previews
Convert images, videos, and documents
Apply image watermarks
Share files for electronic signature
Store and retrieve end-to-end encryption key data
Integrate AI-powered file and content-processing workflows

Developer documentation

The Files.fm API documentation includes endpoint descriptions, authentication details, request parameters, response formats, and examples. The OpenAPI specification can be imported into tools such as Swagger UI, Postman, Insomnia, Stoplight, Redoc, code generators, test tools, and AI coding assistants.

New

MCP connector for AI agents

Files.fm now provides a hosted Model Context Protocol (MCP) endpoint so AI agents can securely work with your files and API documentation.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets LLM agents such as ChatGPT, Claude, Cursor, Codex, and Opencode connect to external tools and data sources in a consistent way. Once connected, the agent can call the Files.fm connector to browse folders, read files, and search your content and our API docs, without leaving the chat.

The connector is read-only: it never uploads, renames, moves, deletes, or shares files, and it only returns data that your access token is allowed to see.

Endpoint https://api.files.fm/api/mcp

Streamable HTTP over POST, JSON-RPC 2.0.

Authentication Authorization: Bearer <user_id>:<api_token>

Create an API access token in your account API keys.

What the agent can do

Browse and inspect your folders and files
Read file contents (within safe size limits)
Search your files and folders by name and metadata
Search the Files.fm API and MCP documentation

Connect your AI agent

Pick your client and add the configuration below. Replace the bearer token with your own token in the format <user_id>:<api_token>.

Add this to your project .cursor/mcp.json (or the global ~/.cursor/mcp.json).

{
  "mcpServers": {
    "filesfm": {
      "url": "https://api.files.fm/api/mcp",
      "headers": {
        "Authorization": "Bearer <user_id>:<api_token>"
      }
    }
  }
}

Add a remote MCP server to ~/.codex/config.toml and export the token as an environment variable.

[mcp_servers.filesfm]
url = "https://api.files.fm/api/mcp"
bearer_token_env_var = "FILESFMMCP_BEARER_TOKEN"

export FILESFMMCP_BEARER_TOKEN="<user_id>:<api_token>"

In a Claude client that supports remote MCP servers or connectors, add the endpoint as a custom connector and set the Authorization header. The exact UI differs by Claude product and release.

URL:  https://api.files.fm/api/mcp
Header:  Authorization: Bearer <user_id>:<api_token>

Add a remote MCP server to your opencode.json configuration.

{
  "mcp": {
    "filesfm": {
      "type": "remote",
      "url": "https://api.files.fm/api/mcp",
      "headers": {
        "Authorization": "Bearer <user_id>:<api_token>"
      }
    }
  }
}

In ChatGPT, open Settings and add a custom connector (Connectors / Developer mode) using the endpoint URL and your bearer token. Availability depends on your ChatGPT plan and the current interface.

URL:  https://api.files.fm/api/mcp
Header:  Authorization: Bearer <user_id>:<api_token>

Full MCP connector reference

Authentication and production access

API access requires a Files.fm account and HTTPS. Depending on the integration, authentication can use supported API credentials or sign-in methods. For production use, higher limits, custom workflows, white-label integrations, or enterprise support, contact the Files.fm team with a short description of your use case.

Contact Files.fm