file-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILE_BRIDGE_TRANSPORT | No | Transport mode: stdio, sse, or http | stdio |
| FILESYSTEM_MCP_ROOT_PATH | No | Root directory for file operations | Current directory |
| FILE_BRIDGE_MAX_FILE_SIZE | No | Max file size for operations | 10MB |
| FILE_BRIDGE_FOLLOW_SYMLINKS | No | Follow symlinks | false |
| FILE_BRIDGE_DEFAULT_ENCODING | No | Text encoding | utf-8 |
| FILE_BRIDGE_ALLOW_ABSOLUTE_PATHS | No | Allow absolute paths outside root | false |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | Read a file from the filesystem. Returns the file content as text. Binary files are returned as base64-encoded strings
with |
| write_fileA | Write content to a file atomically. Creates parent directories by default. Uses atomic write (temp file + rename) by default to prevent partial writes. Supports configurable encoding. |
| list_dirC | List directory contents with optional filtering. Supports glob pattern filtering, recursive listing, hidden file inclusion, and configurable recursion depth. |
| search_filesA | Search file contents using ripgrep (rg). Requires ripgrep to be installed on the system. Supports regex patterns, glob filtering, case sensitivity, context lines, and result limiting. |
| globA | Find files matching a glob pattern. Uses pathlib's glob matching. Supports recursive patterns (**), hidden file filtering, and result limiting. |
| patch_fileA | Apply a targeted patch to a file. Finds all occurrences of |
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 6 tools
Most tools have clear boundaries, but list_dir and glob overlap significantly: list_dir supports glob filtering, and glob finds files matching patterns, making it easy for an agent to confuse them. read_file, write_file, patch_file, and search_files are otherwise distinct.
Most tools follow a consistent verb_noun pattern like read_file, write_file, and search_files. The exception is glob, which uses a domain-specific single-word name rather than a verb_noun form, creating a minor deviation.
Six tools is a well-scoped size for a file manipulation server. Each tool targets a core file operation without unnecessary redundancy or bloat.
The set covers read, write, patch, listing, searching, and glob matching, which supports most common file workflows. Missing operations like delete, move, or stat are minor gaps that agents can typically work around with existing tools.