xserver-files-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XSERVER_FILES_CONFIG | Yes | Absolute path to the configuration JSON file (e.g., /home/user/.config/xserver-files-mcp/config.json) |
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_serversA | List configured XServer connection profiles and domain roots without connecting to SFTP. |
| list_rootsA | List configured domain roots for a server profile. |
| discover_rootsA | Scan the server home directory for domains with public_html and show which ones are not yet configured. Use add_root to register any you want to manage. |
| add_rootA | Register a new domain root for a server profile. Infers the remote path from the server username if not specified, verifies the directory exists via SFTP, and saves to the config file. |
| init_site_workspaceA | Create the local workspace directory for a configured domain outside this repository and add a protective .gitignore. |
| list_filesA | List files under a configured domain root over SFTP. |
| read_fileB | Read a UTF-8 text file under a configured domain root over SFTP. |
| pull_file_to_workspaceA | Read one remote UTF-8 file and write it under the matching local site workspace path. Existing local files are backed up by default. |
| push_file_from_workspaceA | Read one local workspace file and write it to the matching remote path. Existing remote files are backed up by default. |
| backup_fileA | Create a timestamped dotfile backup next to a remote file. |
| write_fileA | Write a UTF-8 text file under a configured domain root. Existing files are backed up by default. |
| replace_in_fileA | Read a file, replace all exact text matches, and write it back with backup by default. |
| set_domain_redirectA | Insert or update a marked .htaccess 301 redirect block for a configured source domain. Creates a backup by default. |
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 13 tools
Most tools have clear distinct purposes (listing, reading, writing, backing up, configuring). However, pull_file_to_workspace overlaps with read_file (both read remote content) and push_file_from_workspace overlaps with write_file (both write remote), which could cause misselection without careful descriptions.
All tool names follow a consistent snake_case verb_noun pattern (e.g., list_files, read_file, write_file, set_domain_redirect). Even the longer names like pull_file_to_workspace and push_file_from_workspace maintain the pattern with clear prepositions, so the naming convention is uniform.
13 tools is well-scoped for a file management server covering configuration, file operations, backups, and workspace sync. Each tool addresses a specific need without unnecessary bloat, making the count appropriate for the domain.
The tool surface covers core file operations (create, read, update) and backups, but notably lacks a delete tool and directory management (mkdir/move/copy). This is a significant gap for a file management server, as agents cannot complete full file lifecycle workflows.