FileN-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILEN_EMAIL | No | Your Filen account email, used for login instead of an API key. | |
| FILEN_API_KEY | No | Your Filen API key (Settings → Developer). Preferred authentication option. | |
| FILEN_2FA_CODE | No | Optional 2FA code, required if your Filen account has two-factor authentication enabled. | |
| FILEN_PASSWORD | No | Your Filen account password, used with FILEN_EMAIL for login. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_directoryB | List the entries of a Filen cloud directory. Paths are absolute, starting at '/'. |
| statA | Get metadata (type, uuid, size, timestamps) of a file or directory in the Filen cloud. |
| read_fileA | Read a text file from the Filen cloud and return its UTF-8 content. Refuses files that are not regular files or larger than 5 MB (use download_file for those). |
| search_filesB | Search the Filen cloud for files/directories whose path contains the query (case-insensitive substring match). |
| write_fileB | Write UTF-8 text content to a file in the Filen cloud, creating or overwriting it. Parent directories are created automatically. |
| upload_fileA | Upload a local file (or directory) from the machine running this server into the Filen cloud. Parent directories are created automatically. |
| download_fileA | Download a file (or directory) from the Filen cloud to a local destination path on the machine running this server. |
| create_folderB | Create a folder in the Filen cloud. Intermediate directories are created recursively if missing. |
| delete_itemA | Delete a file or directory from the Filen cloud. By default the item is moved to the trash; set permanent=true to delete it permanently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool maps to a distinct operation, but two pairs have adjacent purposes: write_file vs upload_file (both create content) and read_file vs download_file (both retrieve content). The descriptions disambiguate them well (read_file explicitly points to download_file for large/binary files), so confusion is minor.
Nearly all tools follow a verb_noun pattern (list_directory, read_file, search_files, write_file, upload_file, download_file, create_folder, delete_item). The lone exception is 'stat', which breaks the pattern as a bare verb, but it is a recognizable filesystem convention.
Nine tools is well-scoped for a cloud file storage server, covering listing, metadata, reading, writing, transferring, folder creation, and deletion without redundancy. Every tool earns its place.
Core CRUD and transfer operations are covered, but notable gaps remain: there is no move/rename or copy tool, and delete_item mentions a trash but there is no restore-from-trash or list-trash operation. Agents can work around these (e.g. download+upload to move) but not the trash dead end.