seafile-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEAFILE_MCP_MODE | No | Safety mode: read_only, safe_write (default), or full. | safe_write |
| SEAFILE_SERVER_URL | Yes | The base URL of the Seafile server (no trailing slash). This is required. | |
| SEAFILE_VAULT_PATH | No | Path to the vault file where user tokens are stored. Defaults to ~/.seafile-mcp/vault.json. | ~/.seafile-mcp/vault.json |
| SEAFILE_ACCOUNT_TOKEN | No | Optional single-user fallback account token, used when no per-user token is provided via the vault. | |
| SEAFILE_REPO_TOKENS_JSON | No | Optional single-user fallback JSON object mapping library names to API tokens. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_loginA | Validate user_id+password against Seafile and issue a full-scope session token. Password is used once, never stored. |
| auth_register_libraryB | Validate a library API token; bootstrap a scoped session or attach the library to an existing one. Returns the session token. |
| auth_reauthB | Refresh a session after a password change. |
| auth_rotateC | Replace a session token, keeping its credentials. |
| auth_revokeC | Delete a session. |
| auth_add_libraryC | Attach another library token to a session. |
| auth_remove_libraryC | Detach a library token from a session. |
| auth_statusB | Show a session's scope and libraries (nothing secret). |
| get_auth_helpA | Explain how to obtain Seafile account and library API tokens. |
| list_librariesB | List libraries visible to the account token. lib_type: mine, shared, group, mine-group, public (default: all). |
| get_library_infoC | Get details of one library, by repo_id or name. |
| resolve_libraryC | Resolve a library name to its repo_id (account token only). |
| list_directoryC | List a directory. entry_type: 'f' files, 'd' folders. |
| get_file_detailC | Get file metadata (account token only). |
| read_fileC | Read a text file. Binary files return metadata + download link. |
| get_download_linkC | Get a download URL for a file. |
| search_filesB | Search files (account token only; needs search on server). |
| create_libraryD | Create a library (password -> encrypted). |
| rename_libraryD | Rename a library. |
| create_directoryC | Create a folder. |
| upload_fileC | Upload/create a file (text or base64). |
| update_fileC | Overwrite a file (new version in history). |
| rename_itemC | Rename a file or folder (repo token: folders only). |
| move_itemC | Move a file or folder (account token only). |
| copy_itemC | Copy a file or folder (account token only). |
| create_share_linkB | Create a public share link for a file/folder (non-encrypted libraries only). |
| list_share_linksC | List share links, optionally filtered by library/path. |
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 27 tools
Each tool has a clearly distinct purpose: auth operations, library management, file operations, and share links are all cleanly separated. Even similar tools like upload_file vs update_file or rename_library vs rename_item have unambiguous boundaries. No two tools could be confused.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_libraries, create_directory, auth_rotate). The auth_ prefix groups session tools, while resource-specific verbs (list, get, create, update, rename, move, copy) are applied uniformly. No mixed conventions or vague verbs.
27 tools is slightly above the typical heavy threshold, but each tool addresses a distinct operation needed for a full file server integration (auth, libraries, files, shares). While the count feels a bit large, the scope justifies it, and the tools are all useful without redundancy.
The tool surface lacks delete operations for files, folders, libraries, and share links, which are essential for a complete file management lifecycle. Users can create, read, update, move, and copy but cannot remove anything, leaving obvious dead ends in workflows. This is a significant gap that will cause agent failures when cleanup is needed.