Skip to main content
Glama

Related Servers

Alternatives to aegis-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      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
      A
      quality
      B
      maintenance
      Enables coding agents to safely inspect and modify project files within explicitly allowed workspace roots, with controls for file operations, git status/diff, and optionally allowlisted command execution.
      11
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      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.
      8 npm
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to browse, read, search, and write files inside a locked workspace, run asynchronous shell commands, and batch read operations, all with validated caching, health diagnostics, and a SQLite audit trail.
      38
      2,372 npm
      1
      AGPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to safely read and write files in a sandboxed workspace via natural language, with on-demand connection, CVE-hardened path confinement, injection resistance, and full audit logging.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to safely execute commands, run tests, and modify project files inside disposable, policy-enforced Docker sandboxes that are isolated from the host machine and its credentials.
      15
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read/list/search are separate filesystem read operations, exec_python and exec_command target different execution models, and sandbox_inspect_policy is unique. The main potential overlap is fs_write_file versus fs_patch_file, both of which edit files, though their descriptions distinguish full atomic writes from exact-block replacement.

    Naming Consistency4/5

    All names use consistent snake_case and follow a predictable category-prefixed pattern (fs_, exec_, sandbox_). Minor deviation exists because the fs_ tools use verb-object forms while exec_python/exec_command are more namespace-like, but the overall convention is still readable and predictable.

    Tool Count5/5

    Eight tools is well-scoped for a sandboxed filesystem and execution server. Each tool earns its place by covering a distinct operation, with no obvious filler or redundant tools.

    Completeness3/5

    The surface covers read, list, search, write, patch, execution, and policy inspection, which supports most agent workflows. However, common filesystem lifecycle operations such as delete, move/rename, and directory creation are absent, leaving notable gaps for full CRUD coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues