Skip to main content
Glama
MoonTzai

FolderBridge MCP

by MoonTzai

Related Servers

Alternatives to FolderBridge MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      C
      maintenance
      A read-only MCP server that exposes a local code workspace to AI clients via stdio, providing file browsing and text search capabilities with path safety rules.
      1
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.
      4
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A deliberately narrow, approval-gated workspace server that safely reads and writes files and runs allowlisted commands only inside one configured workspace, requiring visible approval for every write, process execution, and file read, with stale-overwrite protection and symlink-escape rejection.
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.
      5
      -
    • A
      license
      A
      quality
      A
      maintenance
      Provides a workspace-safe, read-only bridge between browser-based AI planning/review and local coding agents, enabling structured plan, execution summary, and review handoffs without granting shell, file write, or Git push access.
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides secure, sandboxed file system access for AI assistants to read, write, and manage project files with controlled command execution capabilities, all confined to a designated workspace directory.
      MIT

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues