
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)即時資料:隊長人選、預估出賽、先發陣容、傷病與統計。