Skip to main content
Glama
sangingeum
by sangingeum

Related Servers

Alternatives to filekeeper-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to perform workspace file operations (read/write/recover) with transaction-safe guarantees, durable recovery, and explicit human approval via a separate Broker.
      MIT
    • 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
      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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to compile change plans into canonical, content-addressed manifests, run whole-set checks, and apply writes through a hash-gated two-phase commit with rollback and optional attestation.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM clients to search, read, and patch a trusted source repository with rollback-safe edits, Git operations, and allowlisted validation over stdio or OAuth-protected HTTP. Keeps secrets and arbitrary shell access out of reach while enforcing bounded batched I/O and operator-controlled workspace trust.
      MIT

    TDQS

    A3.9/5.0

    Scored across 25 tools

    Disambiguation4/5

    Tools are largely distinct by resource and action, and descriptions clarify overlapping edit operations such as create vs write and text replacement vs line replacement. A few clusters, especially the multiple granular edit tools and undo_operation vs undo_last, require reading descriptions, but there are no true duplicates.

    Naming Consistency4/5

    Most names follow a predictable resource_action pattern, e.g. file_read, directory_delete, history_diff. Exceptions such as undo_operation, undo_last, and workspace_info are still readable but break the dominant pattern slightly.

    Tool Count3/5

    At 25 tools this is heavy for a file-management server, even though many tools are purposeful and distinct. The granular read/edit/history surface sits at the upper boundary and could likely be consolidated somewhat.

    Completeness5/5

    The surface covers workspace introspection, file and directory reads, search, metadata, file and directory lifecycle operations, line and text editing, patch application, history inspection, and undo with conflict handling. No obvious lifecycle or recovery gaps appear for the stated filekeeper domain.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive