把 Google Drive 与 Dropbox Dash 接入本地 AI 助手的个人工具。
MCP Relay 是一个运行在开发者本人 macOS 设备上的本地命令行程序。它通过 Model Context Protocol 与本机的 AI 助手通信，让助手能够检索和阅读开发者自己云端存储中的资料。
它不是面向公众的服务：没有服务器端组件，没有网页界面，不注册账号， 也不为开发者本人以外的任何人提供访问。程序仅在助手需要时启动，用完即退出，不常驻后台。
通过 Google Drive API 检索与阅读文件。申请的权限只有一项：
drive.readonly（只读）。
提供四个能力：按关键词搜索文件、列出最近修改的文件、查看文件元数据、读取文件正文。 Google 文档导出为 Markdown、表格导出为 CSV、演示文稿导出为纯文本；纯文本类文件直接读取。 PDF、Office 文档、图片与音视频不做解析，会明确返回「不支持的二进制格式」。
作为一层透明中继连接 Dropbox 官方的 Dash MCP 服务。本工具在这一侧 不实现任何业务功能：搜索、内容读取等能力全部来自 Dropbox 上游， 原样转发，不筛选、不改写、不缓存。
Google 侧的只读是技术上的限制而非承诺：授权令牌本身不具备写入能力， 因此程序无法创建、修改、删除文件或更改共享设置。
刷新令牌保存在本机 macOS 钥匙串；访问令牌只存在于进程内存。程序不建立数据库、不建索引、 不缓存文件正文，也不包含任何分析或遥测功能。
完整说明见 隐私说明。
A personal tool that connects Google Drive and Dropbox Dash to a local AI assistant.
MCP Relay is a local command-line program running on the developer's own macOS machine. It speaks the Model Context Protocol to a local AI assistant, letting that assistant search and read the developer's own cloud-stored documents.
It is not a public service: there is no server-side component, no web interface, no account registration, and no access for anyone other than the developer. The program starts only when the assistant needs it and exits afterwards; nothing runs in the background.
Searches and reads files through the Google Drive API. It requests exactly one scope:
drive.readonly.
Four capabilities: search files by keyword, list recently modified files, inspect file metadata, and read file contents. Google Docs are exported as Markdown, Sheets as CSV, Slides as plain text; plain-text files are read directly. PDFs, Office documents, images and media are not parsed — the tool returns an explicit "unsupported binary format" error.
A transparent relay to Dropbox's official Dash MCP service. On this side the tool implements no functionality of its own: search and content-reading capabilities all come from Dropbox upstream and are forwarded verbatim — not filtered, not rewritten, not cached.
Read-only access on the Google side is a technical constraint rather than a promise: the token itself cannot write, so the program cannot create, modify or delete files, nor change sharing settings.
Refresh tokens are stored in the local macOS Keychain; access tokens exist only in process memory. The program maintains no database, no index and no content cache, and contains no analytics or telemetry.
Full details in the privacy policy.