worksmobile-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKS_CLIENT_ID | Yes | OAuth client ID from the WORKS Developer Console. | |
| WORKS_PRIVATE_KEY | No | Private key (PEM content) for the service account. | |
| WORKS_CLIENT_SECRET | Yes | OAuth client secret from the WORKS Developer Console. | |
| WORKS_DELEGATED_USER | Yes | Email of the user to delegate to (default user for API calls). | |
| WORKS_SERVICE_ACCOUNT | Yes | Email address of the service account for delegation. | |
| WORKS_PRIVATE_KEY_PATH | No | Path to the private key (PEM) file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| works_drives_listB | List shared drives (id, name, accessibleRange, permissionType, masters). |
| works_drive_getB | Get one shared drive's settings (accessibleRange TENANT/DOMAIN/MEMBER, permissionType). |
| works_files_listB | List files/folders. With sharedrive_id: that shared drive; else the delegated user's My Drive. |
| works_perms_listA | List drive-level (or, with folder_id, folder-level) permissions. |
| works_perm_grantA | Grant READ/WRITE to a member (drive-level, or folder-level with folder_id). Requires confirm=true. |
| works_perm_revokeA | Delete ONE permission by perm_id or target_email. Bulk delete is unsupported by design. Requires confirm=true. |
| works_folder_enableA | Enable folder-level permissions. WARNING: breaks inheritance (masters-only until granted). Requires confirm=true. |
| works_folder_disableA | Disable folder-level permissions. WARNING: drops folder grants, restores inheritance. Requires confirm=true. |
| works_file_downloadA | Download a file to a local path (follows the storage redirect with auth). |
| works_file_uploadB | Upload a local file into a My Drive folder (2-step metadata+PUT flow). |
| works_folder_createA | Create a folder in the delegated user's My Drive (root if no parent). |
| works_share_createA | Share a My Drive folder so it appears in the recipient's 'shared with me'. My Drive only (not shared drives). Requires confirm=true. |
| works_share_deleteC | Remove sharing from a My Drive folder. Requires confirm=true. |
| works_sharedfolders_listA | List a member's 'shared with me' folders (requires that member as delegated user). |
| works_searchC | Search drive files (drive_type_filters e.g. 'SHARE_DRIVE'). |
| works_api_callB | Raw WORKS API escape hatch (path under https://www.worksapis.com/v1.0). Non-GET requires confirm=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
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.
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.
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.
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.