universal-mcp-fs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Read the full contents of a file. Text files are returned as UTF-8 text; binary files are detected automatically and returned as base64. Args:
Returns: file contents as text, or a note that the file is binary with base64 content. Error Handling:
|
| read_file_linesA | Read a specific line range from a file. Useful for large files where reading the whole thing would exceed limits. Args:
Returns: the requested lines, each prefixed with its line number. |
| write_fileA | Create a new file or overwrite an existing one. Parent directories are created automatically. Overwriting an EXISTING file requires interactive user approval (elicitation) — the server will pause and ask the connected client to confirm before proceeding. Args:
Error Handling:
|
| create_directoryA | Create a directory, including any missing parent directories (like mkdir -p). Args:
Returns: confirmation of the created path. No error if the directory already exists. |
| list_directoryA | List the contents of a directory with metadata (type, size, modified date). Args:
Returns: a listing with one entry per line: type, size, modified date, name. |
| move_fileA | Move or rename a file or directory. ALWAYS requires interactive user approval before proceeding. Args:
Error Handling:
|
| copy_fileA | Copy a file or directory (recursively for directories). Does not modify the source, so no approval is required. Args:
|
| delete_fileA | Permanently delete a single file. ALWAYS requires interactive user approval before proceeding — this cannot be undone. Args:
|
| delete_directoryA | Permanently delete a directory and all its contents, recursively. ALWAYS requires interactive user approval before proceeding — this cannot be undone. Args:
|
| search_filesA | Find files matching a glob pattern within a directory (e.g. "**/.ts", ".log"). Args:
Returns: a list of matching file paths, relative to the search directory. |
| search_contentA | Grep-like search: find a text query across files in a directory, returning matching lines with 2 lines of context before/after. Args:
Returns: matching lines with file path, line number, and surrounding context. |
| run_commandA | Execute a shell command and return its stdout/stderr. ALWAYS requires interactive user approval before running. Args:
Returns: stdout, stderr, and exit code. Error Handling:
|
| run_command_backgroundA | Start a long-running command in the background and return immediately with its process ID. ALWAYS requires interactive user approval before running. Args:
Returns: the process ID (pid), which can be used with list_processes and kill_process. Note: background processes have no timeout, but they are tracked and can be killed with kill_process. They do not survive this server process restarting (e.g. Claude Desktop being closed and reopened). |
| list_processesA | List background processes started via run_command_background during this session, with their status. Returns: a list of tracked processes with PID, command, status, and start time. |
| kill_processA | Terminate a background process previously started with run_command_background. Requires interactive user approval before proceeding. Args:
|
| file_infoA | Get metadata about a file or directory: size, created/modified dates, permissions, and type. Args:
Returns: size in bytes, created/modified timestamps, POSIX permission bits, and whether it's a directory or symlink. |
| system_infoA | Get information about the machine this server is running on: OS, hostname, home directory, Node version, CPU count, and total memory. Returns: a JSON object with platform details. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Prabhas125/universal-mcp-fs'
If you have feedback or need assistance with the MCP directory API, please join our Discord server