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 EU-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.
Three ways to integrate
What you can build
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
- Download folders and selected files as ZIP archives
- 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
- Manage document management tasks, comments and attachments
- 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.
Connect your AI assistant to Files.fm
With the hosted MCP connector, ChatGPT, Claude, Cursor and other AI assistants can find, read and organize your files and work with your document management tasks, always within the permissions of your own account.
MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools and data securely. You add one address to your assistant, sign in to Files.fm and choose what to allow.
What your assistant can do
- Find, list and read your files and folders
- Create folders, upload or import new files, and rename or move files and folders
- Read document management tasks and projects, create and update tasks, add comments and attach files
- Search the Files.fm API and MCP documentation
Your assistant can only do what you approve and what your account is allowed to do. It cannot delete or overwrite files or change sharing settings. Content the assistant reads is processed by your AI provider under its own terms.
Try asking
- Find the latest contract for our client, summarize the open points and save the summary next to it.
- Create a folder for the new project and move the related drafts into it.
- Create tasks for the website launch, assign them to the team and attach the brief.
Connect your assistant
In ChatGPT settings, add a custom connector with this server address, then sign in to Files.fm when asked. Custom connectors depend on your ChatGPT plan.
https://files.fm/mcp
In Claude, add a custom connector with this server address and sign in to Files.fm. Menu names can differ between Claude apps and plans. In Claude Code, run the command below.
https://files.fm/mcp
claude mcp add --transport http filesfm https://files.fm/mcp
Add this to your project .cursor/mcp.json (or the global ~/.cursor/mcp.json). Cursor opens the Files.fm sign-in when you first use the connector.
{
"mcpServers": {
"filesfm": {
"url": "https://files.fm/mcp"
}
}
}
Add the server to ~/.codex/config.toml, then sign in with the login command.
[mcp_servers.filesfm]
url = "https://files.fm/mcp"
codex mcp login filesfm
Most MCP clients only need the server address and open the Files.fm sign-in automatically. Clients that cannot sign in can send a Files.fm API key in the Authorization header instead.
URL: https://files.fm/mcp
Header (API key only): Authorization: Bearer <user_id>:<api_token>
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.
API keys for the REST and DMS APIs are created in your account settings and are available on paid plans and business accounts. AI assistants connect through the MCP sign-in and do not need a key. Manage API keys