Skip to main content
Glama

Related Servers

Alternatives to ForgeGuard MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      A
      maintenance
      Enables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.
      14
      3
      -
    • 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.
      3 npm
      6
      MIT
    • 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
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI clients like ChatGPT or Codex to manage files and local Git repositories within an explicitly authorized workspace, with server-enforced path boundary checks and optional remote Git operations.
      18
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool maps to a distinct operation and resource type: workspace registration, file read/write/patch, git read-only inspection, directory/search, and process execution. Even potentially similar tools like file_patch and file_write are clearly separated by exact-match replacement versus full-file write.

    Naming Consistency3/5

    All names use lowercase underscores, but the convention is mixed: some are verb-final like file_read and process_run, while others are noun compounds like git_status, directory_tree, and code_search. This is readable but not as predictable as a uniform verb_noun pattern.

    Tool Count5/5

    Eleven tools is well-scoped for a secure file/git/process workspace server. Each tool has a distinct purpose, and none feel redundant or unnecessary.

    Completeness4/5

    The core workflows of registering workspaces, reading/writing/patching files, searching, and inspecting git state are covered. Minor gaps like no project unregister or file deletion are workable but not fatal for typical guarded agent tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive