Skip to main content
Glama
p-united
by p-united

Related Servers

Alternatives to Simple MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A TypeScript MCP server port of Anthropic's filesystem editing tools, allowing file manipulation via client-approved operations without automated writes to prevent system harm.
      5
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Standalone TypeScript MCP server for filesystem operations with robust security, encoding support, and cross-platform path handling.
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A sandboxed file-access MCP server for Claude Desktop, enabling safe read/write access to selected directories with atomic verified writes, undo, and read-only git operations.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local Model Context Protocol (MCP) server that exposes custom tools to Claude Desktop, enabling direct interaction with your local environment. It provides a framework for building and integrating custom TypeScript tools into the Claude interface.
      6 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A secure MCP server that allows Claude to read and write local files on your machine with explicit approval gating for each access.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Claude Desktop to perform file operations like reading, writing, listing directories, and managing files through natural language commands.
      MIT

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create_sample_file is for generating test files, get_allowed_paths lists accessible directories, get_system_info retrieves system metadata, list_directory shows directory contents, read_file reads file content, and write_file writes to files. There is no overlap in functionality, making tool selection straightforward.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: create_sample_file, get_allowed_paths, get_system_info, list_directory, read_file, and write_file. This uniformity enhances readability and predictability across the tool set.

    Tool Count5/5

    With 6 tools, the server is well-scoped for file and system operations, covering creation, reading, writing, listing, and information retrieval. Each tool serves a distinct role without redundancy, making the count appropriate for the domain.

    Completeness4/5

    The tool set provides strong coverage for basic file operations and system queries, including create, read, write, list, and info retrieval. A minor gap exists in update or delete operations for files, but agents can work around this using write_file for updates, and the domain is reasonably complete for a simple server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues