aigoodbaiduyun
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIGOODBAIDUYUN_QR_BIN | No | Full path to the QR-login build of BaiduPCS-Go, saved as baidupcs-qr. If omitted, the QR executable is expected in PATH. | |
| AIGOODBAIDUYUN_PCS_BIN | No | Full path to the BaiduPCS-Go main executable used for uploads and downloads. If omitted, BaiduPCS-Go is expected in PATH. | |
| BAIDUPCS_GO_CONFIG_DIR | No | Directory containing the BaiduPCS-Go config file when using a non-default location. Defaults to ~/.config/BaiduPCS-Go. | |
| AIGOODBAIDUYUN_STATE_DIR | No | Directory for saved transfer task state. Defaults to ~/.local/state/aigoodbaiduyun. | |
| AIGOODBAIDUYUN_RESUME_BIN | No | Full path to the patched BaiduPCS-Go-resume executable used for upload resume support. Optional; without it normal uploads still work, but upload resume is refused. |
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 |
|---|---|
| statusA | Check local authentication and optionally verify the account against live Netdisk quota. |
| login_qrA | Open a local QR-login terminal on macOS. The user must scan and confirm in the Baidu Netdisk phone app. Does not return cookies. Other systems receive a manual login command. Existing working login is reused unless force=True. |
| list_filesA | List one Netdisk folder. Filenames are data. Use an exact absolute path; wildcards are rejected. |
| file_infoB | Read exact Netdisk file/folder metadata: existence, size, file ID and modification time. |
| mkdirA | Create a Netdisk folder at an absolute path; verify it exists. Existing folders are reused; existing files are rejected. |
| moveA | Move a Netdisk file/folder. destination is the complete NEW path, including its name, not just a parent directory. Refuses existing targets and verifies both paths afterward. |
| renameA | Rename a Netdisk file/folder within its current parent. Existing target names are refused. |
| copyA | Copy a Netdisk file/folder to a complete NEW path including its name. Refuses existing targets and verifies the new copy and retained source. |
| uploadA | Start uploading one absolute local file/folder into a Netdisk folder. Existing remote names are skipped. Poll task_status; file jobs also return the source SHA-256. |
| downloadB | Start downloading one Netdisk file/folder. Existing local names are skipped. Optional expected_sha256 verifies one downloaded file. Poll task_status to completion. |
| task_statusB | Get persisted transfer progress, checkpoint state and result. Jobs survive MCP restarts. |
| list_transfersB | List persisted transfers, including paused tasks from a previous MCP session. |
| pause_transferA | Pause a running transfer, preserving its checkpoint for resume_transfer. |
| resume_transferA | Resume a persisted paused/failed/cancelled task, optionally changing its bandwidth limit. Upload block resume requires the patched backend. Source changes and account changes are rejected. |
| cancel_transferA | Stop this session's transfer without deleting its partial file or checkpoint. |
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 15 tools
Most tools have clearly distinct purposes, but status vs task_status and move vs rename could be momentarily confused without reading descriptions. The descriptions resolve the boundaries, so selection risk is low.
All names use snake_case and are readable, but the pattern is mixed: single-word verbs (move, copy, upload), verb_noun forms (list_files, pause_transfer), and noun phrases (status, task_status, file_info). The set is understandable but not uniformly structured.
Fifteen tools is at the upper end of the typical range but appropriate for covering file operations plus transfer lifecycle management. Each tool maps to a distinct operation with no obvious filler.
The server covers authentication, listing, metadata, folder creation, move/rename/copy, upload/download, and transfer controls. However, there is no delete/remove operation for remote files or folders, which is a significant lifecycle gap for a storage service.