MCP Relay 隐私说明

最后更新：2026 年 9 月 4 日

MCP Relay 是一个运行在开发者本人 macOS 设备上的本地命令行工具，用于把 Google Drive 与 Dropbox Dash 的内容接入本地 AI 助手。它不是面向公众的服务，没有服务器端组件，也不为开发者本人以外的任何人提供访问。

访问哪些数据

Google 账号方面，本应用仅申请一项权限：

https://www.googleapis.com/auth/drive.readonly —— 只读访问 Google 云端硬盘

该权限在技术上不具备写入能力：本应用无法创建、修改、删除、移动文件，也无法更改共享设置。这不是靠自我约束，而是由授权令牌本身的范围决定的。

本应用同时可连接 Dropbox Dash（权限为 account_info.read、 dash/content.read、dash/content.write），该部分与 Google 账号数据无关。

数据存储在哪里

刷新令牌（refresh token）与 OAuth 客户端凭据存放在本机 macOS 钥匙串中，条目标识为 service = mcp-relay。
访问令牌（access token）仅存在于进程内存，进程结束即消失，从不落盘。
文件内容不被保存。本应用不建立数据库、不建立索引、不缓存文件正文。读取到的内容仅在本次调用中经由标准输入输出传给本机的 AI 助手，随即丢弃。

数据传输到哪里

本应用在代码层面限定了可访问的主机，除下列地址外无法发起任何网络请求：

Google：accounts.google.com、oauth2.googleapis.com、www.googleapis.com
Dropbox：www.dropbox.com、api.dropboxapi.com、mcp.dropbox.com

不存在任何第三方服务器、分析服务或遥测上报。您的文件内容只在 Google 的接口与本机进程之间流动。

日志

本应用向标准错误输出诊断日志，内容限于接口名称、HTTP 状态码、耗时与连接状态。访问令牌、刷新令牌、客户端密钥、授权码与文件正文均被明确排除在日志之外，调试模式亦不例外。

撤销授权

您可以随时在 Google 账号的第三方应用页面撤销本应用的访问权限。在本机执行 mcp-relay logout google-drive 会删除钥匙串中保存的凭据。

联系方式

如有疑问，请联系 zhangbaiyu@gmail.com。

MCP Relay Privacy Policy

Last updated: 4 September 2026

MCP Relay is a local command-line tool that runs on the developer's own macOS machine. It connects Google Drive and Dropbox Dash content to a local AI assistant. It is not a public service, has no server-side component, and is not made available to anyone other than the developer.

What data is accessed

For Google accounts, the application requests exactly one scope:

https://www.googleapis.com/auth/drive.readonly — read-only access to Google Drive

This scope is technically incapable of writing: the application cannot create, modify, delete or move files, nor change sharing settings. This is enforced by the token itself, not by convention.

The application can also connect to Dropbox Dash (scopes account_info.read, dash/content.read, dash/content.write). That connection is unrelated to Google account data.

Where data is stored

Refresh tokens and OAuth client credentials are stored in the local macOS Keychain under service = mcp-relay.
Access tokens exist only in process memory and are discarded when the process exits. They are never written to disk.
File contents are not retained. The application maintains no database, no index and no content cache. Retrieved content is passed over stdio to the local AI assistant for that single call and then discarded.

Where data is transmitted

The application enforces a host allowlist in code and cannot reach any other host:

Google: accounts.google.com, oauth2.googleapis.com, www.googleapis.com
Dropbox: www.dropbox.com, api.dropboxapi.com, mcp.dropbox.com

There are no third-party servers, analytics services or telemetry. Your file content moves only between Google's APIs and the local process.

Logging

Diagnostic logs are written to standard error and are limited to endpoint names, HTTP status codes, timings and connection state. Access tokens, refresh tokens, client secrets, authorization codes and file contents are explicitly excluded, including in debug mode.

Revoking access

You may revoke this application's access at any time from your Google Account third-party apps page. Running mcp-relay logout google-drive locally deletes the stored credential from the Keychain.

Contact

Questions: zhangbaiyu@gmail.com