UC Drive

Access personal UC Drive files with an authenticated browser Cookie, including browsing, uploads, downloads, and directory management.

Adapter type: uc. See Common configuration for mounting instructions.

Setup

Sign in to UC Drive and open Network in developer tools.
Refresh files, select an actual drive API request, and copy its complete Cookie header value.
Set cookie without the Cookie: prefix; do not copy only one individual cookie.
Use root_fid: "0" for the root, or obtain a subfolder’s parent FID from its listing request.

Configuration

Field	Type	Required	Default	Description
`cookie`	password	Yes	—	Complete Cookie request header value from an authenticated account, without the Cookie: prefix.
`root_fid`	string	No	`"0"`	Backend root folder FID as a string.
`only_list_video_file`	boolean	No	`false`	Filter listings to video files; disable to see other files.

Example

This is a config object. In the admin form, fill the corresponding fields rather than pasting the whole object. Replace credential placeholders with your own values.

json

{
  "cookie": "YOUR_COMPLETE_COOKIE",
  "root_fid": "0",
  "only_list_video_file": false
}

Behavior and limitations

UC resolves sub_path relative to root_fid.
UC does not expose Quark’s use_transcoding_address option and uses original-file downloads.
only_list_video_file hides non-video files; keep it false for general file management.
Cookie lifetime depends on the account session. Update it on authentication errors rather than on a fixed schedule.

Troubleshooting

Login expired: copy a fresh complete Cookie from an authenticated drive API request.
No files: verify the FID and disable the video-only filter.
Downloads limited or slow: check account entitlements, upstream throttling, and connectivity; avoid rapid repeated retries.

References

External documentation provides service and authorization context. Use this page and the current Foxel adapter for configuration fields and limitations.