drivelift
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRIVELIFT_CLIENT_ID | No | client_secret.json の代わりにクライアント ID を渡す（.mcp.json の env 用） | |
| DRIVELIFT_CONFIG_DIR | No | 設定ディレクトリの変更（デフォルト: ~/.config/drivelift） | |
| DRIVELIFT_CLIENT_SECRET | No | client_secret.json の代わりにクライアントシークレットを渡す（.mcp.json の env 用） |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusA | Report whether drivelift can upload to Google Drive right now. Returns state (no_client / no_token / token_invalid / api_disabled / ready), a message, next_steps, and urls. When not ready, relay next_steps to the user verbatim — they contain the exact Google Cloud Console links, a gcloud_setup hint when gcloud is installed, and a ready-made mv command when a downloaded client JSON is found in ~/Downloads. console_form lists sample values for every Console field in steps 3-4; show it to the user as a table so they can fill the forms without guessing. drivelift uses a bring-your-own OAuth client (Desktop app type) and the drive.file scope only. |
| auth_startA | Begin the OAuth sign-in. Opens the Google consent page in the user's browser (loopback redirect on 127.0.0.1) and waits up to wait_seconds (default 90) for the user to finish; if they do, the result is state: completed and no further call is needed. Otherwise state: pending — call auth_status (with wait_seconds) to keep waiting. Requires an OAuth client (see status). |
| auth_statusA | Report the state of the sign-in started by auth_start: idle / pending / completed / failed. With wait_seconds it blocks until the sign-in settles or the time runs out. |
| import_client_secretA | Copy a downloaded OAuth client JSON (Desktop app type) into drivelift's config directory. Pass the file path; the secret itself never enters the conversation. Without a path, it only lists client_secret*.json candidates in ~/Downloads (newest first) and copies nothing — confirm with the user, then call again with the chosen path. |
| gcloud_setupA | For users who have the gcloud CLI: prepare a Google Cloud project and enable the Drive API on the user's behalf. Without confirm it only reports what it would run (planned_commands) — show that to the user and ask for approval. With confirm: true it runs those commands (and |
| uploadA | Upload a local file to Google Drive and return its URL. By default (convert: auto) spreadsheets (xlsx/csv/tsv/ods) become Google Sheets, documents (docx/md/txt/html/rtf/odt) become Google Docs, and slides (pptx/odp) become Google Slides via Drive's own import, which carries over most formatting. Other files are stored as-is. Files go to My Drive root unless folder_id is given. If drivelift is not set up, the error carries next_steps to relay to the user. |
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 6 tools
Each tool has a clearly distinct purpose: status reports readiness, auth_start/auth_status manage the OAuth flow, import_client_secret handles client credentials, gcloud_setup automates project preparation, and upload performs the core action. No overlapping or ambiguous tools.
All tool names follow a consistent lowercase_with_underscores style, with clear verbs (auth_start, import_client_secret, upload) and descriptive nouns (status, auth_status, gcloud_setup). The naming is uniform and intuitive, with no mixed conventions.
With 6 tools, the set is well-scoped for the server's purpose of uploading files to Google Drive with full setup and authentication support. Each tool earns its place, neither too sparse nor overwhelming.
The tool surface covers the entire lifecycle from readiness checks, authentication (both manual and gcloud-assisted), credential import, and upload. There are no dead ends or missing operations for the stated domain.