Skip to main content
Glama
bartosz-kuc

honest-drive-mcp

by bartosz-kuc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to honest-drive-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-google-gdrive

      sleepytimeshon
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to list, read, create, and manage files in Google Drive. It features automatic conversion of Google Workspace formats into Markdown, CSV, and plain text for seamless integration with AI workflows.
      35 npm
      MIT

    • google-services-mcp

      nabheet
      A
      license
      B
      quality
      A
      maintenance
      MCP server that gives AI agents direct access to Google services including Gmail, Calendar, Drive, and more, with multi-account OAuth support. Enables reading and sending email, managing calendar events, and interacting with Google files through natural language.
      60
      22 npm
      1
      MIT

    • gdocs-mcp

      dasasian
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI agents to treat Google Docs like local files: read, edit, manage suggestions and comments, and work across tabs and multiple Google accounts.
      32
      37 npm
      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 8 tools

    Disambiguation4/5

    Each tool maps to a distinct action-resource pair, but read_file (content) and get_file (metadata) are close enough that an agent must read descriptions carefully. The permission trio (share_file, list_permissions, remove_permission) is cleanly separated.

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout: read_file, create_file, create_folder, list_files, get_file, share_file, list_permissions, remove_permission. No mixed conventions or vague verbs.

    Tool Count5/5

    Eight tools is well-scoped for a Drive file-management surface, with each tool earning its place across read, create, list, and permission operations.

    Completeness3/5

    Covers read/create/list/get plus permission management, but there is no delete_file, no update_file (rename/move/modify), and no move operation. These are common Drive workflows whose absence will force agents into dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources