Skip to main content
Glama
abcamus

sync-vault-agent

by abcamus

sync-vault-agent

让你的 AI 直接读写百度网盘、阿里云盘、115、夸克、OneDrive

npm version npm downloads License Dependencies GitHub

⚠️ Want to see it in action? Add your screenshot at docs/hero.png — or try it now with a free account.

What is this?

When your AI assistant (Claude Code, Cursor, Windsurf) needs to find a file on your cloud drive — a quarterly report on Baidu, a meeting note on OneDrive — you want it to just find it. Not switch between 5 browser tabs, not download and re-upload.

sync-vault-agent is the missing link. An MCP server that connects AI clients to your cloud storage accounts. One npm install, one config, and your AI can search, read, and manage files across 5 cloud drives as if they were local.

English · 中文

Demo

"Find the Q4 report in Baidu, search all drives for budget.xlsx, read yesterday's meeting notes from OneDrive"

Supported Drives

Drive

Auth

Status

百度网盘 (Baidu)

OAuth

阿里云盘 (Aliyun)

OAuth

115 网盘

OAuth

OneDrive

OAuth

夸克网盘 (Quark)

Cookie

Quick Start

# 1. Install the agent globally
npm install -g sync-vault-agent

# 2. Initialize (creates config + opens browser for login)
mcp-agent init

# 3. Add to your AI client's mcp.json

Add to claude_desktop_config.json, ~/.cursor/mcp.json, or VS Code Continue config:

{
  "mcpServers": {
    "unidrive": {
      "command": "mcp-agent",
      "args": ["start"]
    }
  }
}

That's it. Restart your AI client and you can start asking questions about your cloud files.

Why sync-vault-agent?

The problem

  • Your AI can only access files on your local machine

  • Cloud drive files are fragmented across 5+ different ecosystems

  • Switching between drive UIs kills productivity

The solution

sync-vault-agent gives your AI a unified gateway to all your cloud storage:

  • Multi-cloud, one agent — connect Baidu, Aliyun, 115, OneDrive, Quark through a single MCP server

  • 10+ AI clients supported — Claude Code, Cursor, Windsurf, VS Code Continue, any MCP-compatible tool

  • 30-second setup — install, init, done

  • Zero dependencies — pure Node.js, no bloated SDKs

  • Secure by design — refresh tokens encrypted server-side, access tokens rotated every 2 hours, agent holds short-lived credentials only

  • Usage dashboard — real-time analytics, per-drive breakdown

Configuration

Config lives at ~/.config/sync-vault/agent.json. Override via env vars:

Variable

Default

Description

SYNC_VAULT_API_KEY

API key from Dashboard

SYNC_VAULT_AUTH_URL

https://auth.sync-vault.com

Auth service URL

SYNC_VAULT_STORE_PATH

~/.config/sync-vault/

Credential store path

Build from Source

git clone https://github.com/abcamus/sync-vault-agent.git
cd sync-vault-agent
npm install
npm run build

Contributing

PRs welcome! Please open an issue first to discuss changes.

License

MIT © Camus Qiu

-
license - not tested
-
quality - not tested
B
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abcamus/sync-vault-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server