
WireCat Google Drive
dev.wirecat由 wirecat.dev 发布v0.61.0更新于 Nov 7, 2026
Google Drive and Docs for agents: search, read and write a local copy. Sign in with drive first.
概览
把选定的 Google Drive 文件夹导入为本地 Markdown 快照,并向助手提供搜索、读取和写入三个 MCP 工具。
- 可以做什么
- 搜索并读取已导入的文档,包括 Google Docs 的全部标签页,并保留原始 Google 链接
- 把文档导出为 Markdown 文件,列出或查看已同步文档及其新鲜度信息
- 同步所选文件夹、管理文件夹范围并保持快照更新
- 为文档添加标签、笔记、身份、事实和记忆,并查看文档上下文与历史
- 调用生成的 Drive、Sheets、Docs 和 Activity API 方法,处理文件、文件夹、评论、权限和修订
- 适用场景
- 适合让助手基于一组指定的 Google Drive 文件夹回答问题,或保留一份可搜索的本地 Docs 与 Sheets 副本,并在重命名和移动后仍能识别来源。也适合希望把文档笔记和记忆与其他 WireCat 数据存放在一起的场景。
- 运行要求
- 需通过 npm 安装本地 CLI,Node 版本为 22.x 系列的 22.16 及以上或 Node 24 及以上。需要 Google 账号并在浏览器中登录,可使用 WireCat 内置的 Google 应用或自建 Desktop 客户端凭据。语义搜索需显式下载约 135 MB 的本地嵌入模型;AI 提取需可选的模型服务商 API 密钥。
安装
在 SourceWeft 中
- 打开 控制台中的 WireCat Google Drive,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
drive-cli
drive imports selected Google Drive folders into local Markdown snapshots and searchable
documents. It reads Google Docs across all tabs, keeps source identity through renames and moves,
and reuses WireCat's shared keyword search and optional local embeddings. Shared tags, notes,
editor identities and evidence-backed memories stay attached to the imported documents.
Drive uses Google's official Node clients. Sources supported now: native Google Docs and Sheets, PDF, docx, xlsx, CSV, TSV, and uploaded Markdown/TXT. Other types and shortcuts are reported as skipped; shortcuts are not followed outside the selected scope.
How it compares with gog, Workspace MCP and rclone, and when another tool fits better: compared with other tools.
Install
Install the compiled CLI with Node 22.16+ on the 22.x line or Node 24+. A source build is not required:
See installation and Google connection. Source builds are for contributors.
drive doctor shows the version, settings file, profiles and paths without signing in, and drive upgrade
installs a newer version with the package manager that installed drive.
drive guide lists scenarios — the commands for a common task, in order — and drive commands --json is the full
command tree. For an agent, drive skill install puts drive's instructions where Claude Code, Codex, Gemini CLI and
OpenClaw look (Hermes with --for hermes), drive personal mcp serve serves three MCP tools (search, read, write) —
--http serves them to ChatGPT and Claude in the browser (remote MCP) — and DRIVE_READ_ONLY=1
refuses every change, as --read-only does.
Sign in and choose folders
Sign in with WireCat's included Google application. Each user approves their own account in the browser. Making a shared Google application public for Drive is complex, so Google may refuse the sign-in; see what to do. You can also create your own Desktop client as explained in the installation guide. Connect your account, then choose a folder:
For Google Cloud setup and an isolated first run, follow the browser sign-in and live validation guide.
Sign-in opens the system browser and receives Google's callback on a temporary loopback port.
--no-browser prints the URL. drive.readonly grants account-wide reading; our selected-folder
scope limits ingestion. Sync reads remote files. Optional remote management commands need a
new sign-in with session start --grant write; history events need session start --grant activity.
Credentials use the OS keyring. Where it fails, drive uses an owner-only private file without
asking and says so once; --credential-storage file chooses the file outright, not recommended. Tokens never enter regular config, output
or diagnostics. Your own Google app replaces the bundled one with session start --client-file or --client-id,
DRIVE_GOOGLE_CLIENT_ID and DRIVE_GOOGLE_CLIENT_SECRET, or the google_client_id setting, in that order. The included Desktop
client identity is public application metadata, separate from private user tokens. If you create
your own Desktop client and leave it in Testing, Google usually ends its sign-ins after seven days.
Google OAuth guide,
Drive permissions.
Use drive work … for another account. Each Google account has one local profile. drive session list
lists configured profiles. session end removes local sign-in while retaining cached data and
configuration so re-login preserves document identities.
Search and export
Search results include the original Google URL. documents show, list and export print synced_at and age_days; a copy older than a day adds missing, next and meta.complete: false. documents show includes each tab's text, ID
and title. Native Markdown exports are saved separately from the all-tab text used for indexing.
Export refuses to overwrite an existing destination file.
Semantic search uses the shared local text model (about 135 MB). Download it once; it needs no profile or sign-in, and every WireCat CLI shares it:
Drive never downloads a model on its own; a missing one is reported. --exact searches words without semantic
retrieval.
Keep it current
A batch is persisted before processing; interrupted work resumes next run. Progress is saved every 25 files or 2 seconds, so a killed sync redoes at most that many. The first walk of the chosen folders is saved as it goes, and an interrupted walk continues from the folders it had not listed yet. The change cursor advances when the batch completes. Incomplete discovery preserves the prior checkpoint and documents. A per-profile heartbeat lock prevents simultaneous syncs and recovers after crashes.
Confirmed removals and scope exits remove sources from search and delete their snapshots. Removing the last selected folder reconciles to an empty cache on the next sync. Unsupported, restricted and oversized sources have explicit coverage status. Transient failures remain pending; a partial sync with errors exits nonzero. Doc IDs, rather than names, distinguish duplicates.
Storage and coverage
The shared path helper chooses platform-appropriate config, data and cache directories under
drive-cli. Override with DRIVE_CONFIG_DIR, DRIVE_STATE_DIR and DRIVE_CACHE_DIR. Snapshots are
profiles/<profile>/documents/<file-id>.md plus private JSON metadata and raw Docs responses.
Documents use the same local WireCat database as Memo, Telegram and MAX. Imports become searchable
across those tools, alongside messages and notes. MESSAGING_STORE selects another database;
WIRECAT_STATE_DIR moves the default WireCat directory. Google sign-ins remain separate.
On first use after an upgrade, Drive rebuilds old document references from its managed snapshots,
without fetching Google. It retains the old database. If that database contains tags, notes,
memories, facts or relationships, Drive refuses to strand them: keep using that file through
MESSAGING_STORE until those annotations are transferred.
Search covers body text, nested tables and footnotes from all tabs. Images, headers, footers, comments and suggested edits are excluded. Image assets are not downloaded. Search text and Google’s native Markdown export are separate representations; inspect the export when layout or tab coverage matters.
One sync reads at most 10,000 entries under the chosen folders, and at most 10,000 changes from Google's change feed; past either, it stops with nothing lost and says what to do. Text caps at 2,000,000 characters and snapshots at 50 MiB, with bounded pagination. Oversized input is refused rather than truncated. Google's native export also has its own 10 MB limit. Documents changing during export remain pending for retry.
Document knowledge and remote actions
AI extraction explicitly sends selected cached text to the configured model. It previews proposals
unless --yes is given; saved proposals include source quotes, snapshot hashes and model authorship.
Use the shared model setup with models set --provider openai --model MODEL_ID. Provider keys
come from the corresponding API-key environment variable and never enter regular configuration.
Source content changes and scope removals mark source-backed memories stale. User notes stay local.
The generated API exposes 85 methods: 64 Drive, 17 Sheets, 3 Docs and 1 Activity. Convenient commands include file listing/copying/moving, trash/restore, folder creation, Docs creation/batch updates, comments, permissions, revisions and Shared Drives. Read grants remain the default. JSON API calls require explicit flags for mutation and permanent deletion; Google still enforces file roles and API policy.
Read the knowledge and API command guide for complete examples, permissions, history limits, AI settings and supported request formats. Contributor checks use isolated sources and mocked provider requests; see the testing guide.
Community
Questions and setup help: join the WireCat Discord. Bugs go to this repository's issues.
来源:README.md,提交 9eea476
工具
0版本历史
9- v0.61.0最新Nov 7, 2026
- v0.60.0Nov 5, 2026
- v0.59.0Nov 3, 2026
- v0.54.3Nov 1, 2026
- v0.54.1Nov 1, 2026
- v0.52.1Oct 31, 2026
- v0.51.0Oct 31, 2026
- v0.47.0Oct 31, 2026
- v0.46.0Oct 29, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Wire 集成
Wire Cash: bank wire fees and transfer costs
cash.wire官方发布者
Wire Cash 让助手查询美国银行公布的境内外电汇手续费、当日截止时间,以及向墨西哥、印度、菲律宾汇款的 World Bank 汇款成本。

TollWire Evidence
由 GitHub 账号 TollWire 发布
本地 MCP 服务器,把智能体的变更、扫描、审批和部署记录到防篡改哈希链日志中,并可校验该日志。

WireCat b24
dev.wirecat
一个本地 CLI 驱动的 MCP 服务器,让助手读取和修改 Bitrix24 门户的 CRM:交易、线索、联系人、公司、销售流程和产品。

SupportWire
由 GitHub 账号 supportwire 发布
托管式 SupportWire MCP 服务器,让助手分诊客服会话、回复客户,并管理客户、任务与团队设置。
Touchline Wire — FPL & Premier League Intelligence
由 GitHub 账号 Steven-Robinson 发布
免认证的 MCP 服务器,为助手提供 2026/27 赛季英超与梦幻英超(FPL)实时数据:队长人选、预计出场、首发阵容、伤病与统计。