A
licenseA
qualityA
maintenanceMCP server for interacting with Google Drive using a service account, restricted to a specific root folder. Supports file operations like search, list, create, update, and read.
4
22 npm
1
MIT
worksmobile-mcp
by z0nam
Related Servers
Alternatives to worksmobile-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProduction-ready MCP server for Google Workspace providing broad coverage across Gmail, Drive, Calendar, Docs, Sheets, and more, with safe-by-default write operations and markdown-to-Google-Docs support.10022 PyPIMIT
- AlicenseAqualityDmaintenanceMCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Enables reading, creating, and editing Google Docs and Sheets, managing comments, reading emails, and viewing calendar events.3425 npm17MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to browse, search, download, and upload files in a NAVER MYBOX drive, plus inspect storage quota and create folders, all paced under the documented API rate limits. Read-and-write only: file deletion and trash management are deliberately not exposed.724 PyPIMIT
- AlicenseAqualityCmaintenanceMCP server enabling file operations (list, search, read, rename, move) on Google Drive and OneDrive.21MIT
- AlicenseAqualityCmaintenanceSelf-hosted MCP server that exposes Synology Drive, Spreadsheet, MailPlus, and Calendar as structured tools for AI agents, enabling file, spreadsheet, email, and calendar management via natural language.3917 npm11MIT
TDQS
B3.4/5.0
Scored across 16 tools
Disambiguation4/5
Most tools have clearly distinct purposes, with only minor potential overlap between works_share_create/works_perm_grant and works_files_list/works_search. The descriptions generally resolve ambiguity adequately.
Naming Consistency4/5
Tools follow a consistent noun_verb pattern (e.g., drive_get, files_list, perm_grant), with the exception of works_search, which lacks a resource prefix. This is a minor deviation from an otherwise predictable naming convention.
Tool Count4/5
16 tools is slightly above the typical 3-15 range, but the scope covers file management, permissions, sharing, and a raw API escape hatch. Each tool serves a distinct purpose, making the count reasonable for the apparent domain.
Completeness3/5
The toolkit covers listing, downloading, uploading, sharing, and permission management well, but lacks file delete, rename, move, and drive lifecycle operations (create/update/delete). These gaps are notable for a file management server.
Maintenance
ActivitySlowing
ResponsivenessNo issues