FolderBridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| read-only | No | When present, starts the server in read-only mode via --read-only. Recommended for safety. | |
| workspace | Yes | Path to a workspace folder. Repeat --workspace to authorize additional folders (up to eight). At least one workspace is required. | |
| capability | No | Name of a global pre-authorized capability (test, build, package-windows, package-android, release-sync, or git-push). Repeat --capability for multiple capabilities. | |
| allow-tasks | No | When present, enables approved per-workspace named tasks via --allow-tasks. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | List the fixed workspace IDs, enabled capabilities, approved tasks, and safety boundary. |
| flight_recorderA | Read FolderBridge's compact local reliability flight recorder. It keeps only the latest 15 minutes with a 20 MiB total cap, records MCP/Tunnel metadata and bounded redacted diagnostics, and never stores full MCP request/response bodies. Use action=status for storage health, recent for a bounded timeline, or errors for warning/error events only. |
| workspaceA | List files, page through UTF-8 text, stream literal search across large UTF-8 files, or page through git status/diff output. When multiple workspaces are configured, pass a workspace_id returned by server_info. All paths are relative; links, credentials, dependencies, and VCS internals are denied. |
| file_infoA | Return bounded metadata and whole-file SHA-256 for a regular file without exposing its bytes; use this SHA before editing large text files. Uses the same workspace confinement, link denial, and sensitive-path policy as text tools. |
| pptx_inspectA | Safely inspect a PPTX inside the selected workspace using Python standard-library ZIP/XML parsing. Returns slide text, diagram-to-slide mappings, dgm:pt points, dgm:cxn connections, and orphan/duplicate diagnostics. Does not execute macros, embedded objects, or workspace code. |
| image_openA | Return one bounded PNG/JPEG/GIF/WebP as MCP image content, either from a direct workspace path or from one exact member inside a workspace ZIP. The archive is never extracted to disk. |
| extensionA | Stable extension gateway. action=list returns a compact pageable catalog of installed/hot-reloaded extensions and action names; action=info returns the full schema for one extension; action=run invokes one declared extension action. Long foreground actions may be transport-safely promoted in-place to a host-owned Job; use action=job_list to rediscover workspace Jobs, action=job_status to inspect completion/runtime health/results, and action=job_cancel to terminate the owned worker process tree. Installing more extensions does not add MCP tool names. External extension code requires exact-hash local approval; globally authorized actions must also be enabled in the FolderBridge extension sidebar. Dynamic workspace adapters are re-evaluated at call time, so later project changes do not require workspace task injection. |
| edit_fileA | Atomically create a UTF-8 file, or edit one using unique exact replacements and a current whole-file SHA-256. workspace(read) returns that SHA for small files; use file_info for larger files. When multiple workspaces are configured, pass the same workspace_id used for inspection. Cannot delete files, edit the local task config, follow links, or access credential-like paths. |
| write_fileA | Host-owned five-action transaction for large whole-file creates or replacements without requiring one giant MCP message. Use begin, then one or more append calls with the exact next UTF-8 byte offset, optionally status, then commit with the complete expected size and SHA-256; abort discards staging. Staging stays outside the workspace, replace mode rechecks the original target SHA at commit, and successful commit uses a same-directory fsync + atomic replace. |
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 targets a distinct resource or operation, but write_file and edit_file both create/edit files and could be confused; descriptions clarify their intended scale (large transactional vs. atomic replacements) and complementary use with file_info. Other tools (image_open, pptx_inspect, extension, flight_recorder) are clearly separate.
Most names are snake_case, but conventions are mixed: verb_noun (write_file, edit_file), noun_verb (image_open, pptx_inspect), and bare nouns (extension, workspace). There is no camelCase chaos, but the inconsistent verb styles prevent top score.
9 tools is well within the 3-15 ideal range and each tool earns its place in the file/workspace/extension domain. No tool appears redundant in count.
Core file operations are covered (read, write, edit, inspect), but there is no delete/remove tool, and no directory-level operations (move, copy, mkdir). These are notable gaps for a file-management server, though agents can work around some by editing to empty or using extensions.