WireCat Google Drive

dev.wirecatPublished by wirecat.devv0.61.0Updated Nov 7, 2026

Google Drive and Docs for agents: search, read and write a local copy. Sign in with drive first.

The publisher's own server: Wire Cash: bank wire fees and transfer costs

Overview

AI-generated overview

Imports selected Google Drive folders into local Markdown snapshots and gives an assistant three MCP tools to search, read and write them.

What you can do
  • Search and read imported documents, including all tabs of Google Docs, with original Google URLs
  • Export documents to Markdown files and list or show synced documents with freshness details
  • Sync chosen folders, manage folder scope and keep snapshots current
  • Attach tags, notes, identities, facts and memories to documents, and inspect document context and history
  • Call generated Drive, Sheets, Docs and Activity API methods for files, folders, comments, permissions and revisions
When to use it
Useful when an assistant should answer questions from a defined set of Google Drive folders, or keep a local, searchable copy of Docs and Sheets that survives renames and moves. Also fits when you want document notes and memories stored alongside other WireCat data.
Requirements
Local CLI installed with npm and Node 22.16+ on the 22.x line or Node 24+. A Google account signed in through the browser, using WireCat's included Google application or your own Desktop client credentials. Optional local embedding model (about 135 MB) downloaded explicitly for semantic search; optional provider API key for AI extraction.
Before you install
Sign-in grants account-wide read access, limited only by the selected-folder scope; write and activity features need a separate sign-in with additional grants. Credentials go to the OS keyring, falling back to a private file. Sync and API commands can change or delete Drive content, and AI extraction sends selected cached text to a configured model provider. Exports refuse to overwrite existing files.

Installation

In SourceWeft

  1. Open WireCat Google Drive in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Google Drive for your AI agents: Docs as local Markdown, search with sources]

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:

sh
npm install -g @wirecat/drive-clidrive --versiondrive --help

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:

sh
drive personal session startdrive personal folders add https://drive.google.com/drive/folders/FOLDER_IDdrive personal sync --json

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

sh
drive personal search 'budget decision' --jsondrive personal search 'budget' --exact --jsondrive personal documents list --jsondrive personal documents show DOC_ID --jsondrive personal documents export DOC_ID --output ./document.mddrive personal status --jsondrive commands sync --json

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:

sh
drive models download e5-smalldrive personal sync --embed

Drive never downloads a model on its own; a missing one is reported. --exact searches words without semantic retrieval.

Keep it current

sh
drive personal sync --limit 200 --jsondrive personal folders remove FOLDER_IDdrive personal sync --json

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

sh
drive personal tags add DOC_ID project-budget reviewdrive personal documents list tag:reviewdrive personal notes add DOC_ID 'Check the assumptions' --title Reviewdrive personal identities list DOC_IDdrive personal documents context DOC_IDdrive personal facts add DOC_ID 'Budget approved for Q4' --type decision --scope workdrive personal memories add DOC_ID 'Q4 budget, in short' --scope work --kind summarydrive personal memories extract DOC_ID --scope workdrive personal documents history DOC_IDdrive api list service:docs

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.

Source: README.md at commit 9eea476

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

9
  1. v0.61.0LatestNov 7, 2026
  2. v0.60.0Nov 5, 2026
  3. v0.59.0Nov 3, 2026
  4. v0.54.3Nov 1, 2026
  5. v0.54.1Nov 1, 2026
  6. v0.52.1Oct 31, 2026
  7. v0.51.0Oct 31, 2026
  8. v0.47.0Oct 31, 2026
  9. v0.46.0Oct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Wire integrations