Skip to main content
Glama

Related Servers

Alternatives to chuk-mcp-vfs

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a secure, constrained filesystem workspace for LLM agents to manage files, notes, and code artifacts via stdio or remote HTTP. It features granular access controls, including extension whitelisting, storage quotas, and immutable paths for safe automated file operations.
      BSD 3-Clause
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to list, read, inspect, write, and precisely edit files and to regex-search a workspace, with every path confined to a sandboxed root directory. Token-saving output such as line-range reads and match locations without line content keeps context use low while guarded writes and ambiguous edits prevent accidental data loss.
      6
      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
    • A
      license
      A
      quality
      A
      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.
      44
      1,549 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      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 agent hosts to perform guarded, undoable filesystem operations confined to registered workspaces: atomic whole-file writes, file and directory create/copy/move/delete, staged literal text and line-range edits, patch application, and search, all journaled with content-addressed blobs. Every mutation returns an operation id and undo availability so history can be inspected and safely reverted with conflict detection, while credential-shaped targets are refused and errors come back as structured data with stable codes.
      25
      MIT

    TDQS

    B3.1/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity, covering specific filesystem operations, workspace management, or checkpoint functions. For example, 'ls' lists directory contents while 'tree' shows a tree structure, and 'workspace_create' creates a workspace versus 'workspace_switch' changes the active one. The descriptions reinforce these distinctions, making misselection unlikely.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as 'checkpoint_create', 'workspace_list', and 'mkdir'. All tools use snake_case with clear, descriptive verbs aligned with their functions, like 'read', 'write', 'find', and 'grep'. There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count4/5

    With 23 tools, the count is slightly high but reasonable for a virtual filesystem server that aims to provide comprehensive file and workspace management. It covers core operations (e.g., read, write, ls), advanced features (e.g., checkpoints, workspaces), and utilities (e.g., grep, find), though it might feel heavy compared to simpler servers. Each tool appears to earn its place without obvious redundancy.

    Completeness5/5

    The tool surface is complete for the virtual filesystem domain, offering full CRUD and lifecycle coverage for files, directories, workspaces, and checkpoints. It includes creation (mkdir, workspace_create), reading (read, ls), updating (write, mv), deletion (rm, workspace_destroy), and management operations (e.g., checkpoint_restore, workspace_switch), with no apparent gaps that would cause agent failures in typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive