Skip to main content
Glama
anyrxo

Proton Drive MCP

by anyrxo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Proton Drive MCP

No user-submitted related servers found.

    Related Servers

    • Filesystem MCP Server

      QuantGeekDev
      F
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol server that extends AI capabilities by providing file system access and management functionalities to Claude or other AI assistants.
      212 npm
      5
      -

    • google-drive-mcp

      software-engineer-mj
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for Google Drive API v3, enabling AI agents like Claude to manage files, folders, and sharing.
      28
      MIT

    • MCP-FileSystem

      dgholamian
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that gives AI assistants secure, sandboxed filesystem access with tools for reading, writing, searching, and managing files and directories.
      MIT

    • MCP Local File Reader

      sworddut
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that allows AI models to safely access and interact with local file systems, enabling reading file contents, listing directories, and retrieving file metadata.
      2 npm
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: check_mount verifies accessibility, create_folder creates folders, delete_file deletes items, get_file_info retrieves metadata, list_files lists contents, read_file reads text files, and write_file writes files. The actions (check, create, delete, get, list, read, write) and targets (mount, folder, file) are well-defined and non-overlapping.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case, such as check_mount, create_folder, delete_file, get_file_info, list_files, read_file, and write_file. The naming is predictable and readable throughout the set, with no deviations in style or convention.

    Tool Count5/5

    With 7 tools, the count is well-scoped for a Proton Drive file management server, covering essential operations without bloat. Each tool earns its place by addressing core needs like mounting, CRUD operations, and file listing, making the set efficient and focused.

    Completeness4/5

    The tool set provides strong coverage for basic file operations, including create, read, update (via write_file), delete, and list, along with mount checking and metadata retrieval. A minor gap exists in update operations for folders (e.g., rename or move), but agents can work around this using delete and create, and core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources