Skip to main content
Glama
MoonTzai

FolderBridge MCP

by MoonTzai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to FolderBridge MCP

No user-submitted related servers found.

    Related Servers

    • mcp-readonly-code-server

      John0615
      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
      -

    • MCPort

      sky32
      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.
      2 npm
      6
      MIT

    • Forge Workspace MCP Server

      mwdk2smb4r-ux
      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

    • github-assistant-mcp

      imshashwatsingh
      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
      -

    • Hua PlanRelay

      lmwacn
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: file operations, editing, reading/searching, metadata, specific format inspection, extension management, and server info. Even edit_file vs write_file are separated by size/chunking, and workspace vs file_info differ in scope. No overlapping or ambiguous tools.

    Naming Consistency3/5

    All names use lowercase with underscores, but the verb/noun order varies: edit_file and write_file use verb_noun, while file_info and server_info use noun_verb, and workspace and extension are bare nouns. This inconsistency makes the pattern less predictable, though still readable.

    Tool Count5/5

    10 tools is well-scoped for a file management and inspection server. Each tool covers a distinct aspect (copy/move, create/edit, read/search, metadata, format inspection, extensions, diagnostics) without redundancy or bloat.

    Completeness3/5

    The surface covers most file lifecycle operations (create, edit, read, copy, move, metadata) but lacks a delete operation. Also missing directory creation and possibly rename (though move may cover that). These are notable gaps for a file management server.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources