Skip to main content
Glama

Related Servers

Alternatives to fsguard-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      C
      maintenance
      Enables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.
      10
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT and Codex to safely work with explicitly authorized local project folders through MCP, providing constrained file reading, searching, patch editing, Git inspection, and whitelisted tasks without exposing arbitrary shell, deletion, or deployment capabilities.
      17
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to read, search, patch, and execute commands in a codebase, including interactive sessions and git operations, with permission modes and safety boundaries.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT or any MCP client to operate safely on a designated workspace by listing, reading, searching, writing, and trashing files, inspecting Git status/log/diff, and optionally running allowlisted executables without a shell.
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes a secure, path-confined bridge to a local workspace and git remotes, enabling MCP clients to search, read, write, reset files, and perform git operations.
      -

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct operation: file read, write, list, search, move; git init, status, stage, commit, diff, log. There is no overlap or ambiguity between tools, enabling reliable selection.

    Naming Consistency4/5

    The naming follows a consistent fs_/git_ prefix pattern with action-oriented verbs. Minor deviation like 'git_repo_status' vs 'git_stage' (noun-verb vs verb-only) creates slight inconsistency but remains predictable.

    Tool Count5/5

    11 tools cover file system and git operations without redundancy. The scope is well-balanced—enough to handle common workflows without overwhelming the agent.

    Completeness3/5

    The file system layer includes create, read, update, list, search, and move, but lacks a delete operation, which is a notable gap. Git coverage is solid for basic workflows but omits branch operations. Overall, a reasonable surface for the intended guarded-root use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues