AI agent이 Google Drive 및 Docs를 검색, 읽기, 쓰기 할 수 있도록 파일을 로컬 Markdown 스냅샷 및 검색 가능한 문서로 가져옵니다.
다른 이름 WireCatLabs/drive-cli, drive-cli, @wirecat/drive-cli
- 스타
- 1
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.69.0
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- Apache-2.0
WireCat Google Drive MCP란?
WireCat Google Drive은(는) MCP server입니다. AI agent이 Google Drive 및 Docs를 검색, 읽기, 쓰기 할 수 있도록 파일을 로컬 Markdown 스냅샷 및 검색 가능한 문서로 가져옵니다.
프로젝트 README에서 생성된 요약
WireCat Google Drive MCP server 정보
WireCat Google Drive는 파일을 로컬 Markdown 스냅샷으로 변환하여 AI agent가 Google Drive 및 Google Docs와 상호작용할 수 있도록 합니다. 이 도구는 에이전트에게 클라우드 문서에 대한 검색 가능하고 구조화된 액세스 권한을 제공해야 하는 개발자 및 AI 사용자를 위해 설계되었습니다. Google Docs, Sheets, PDF, docx, CSV 등 다양한 파일 형식을 지원합니다. 사용자는 CLI를 통해 로컬에서 실행하거나 --http 플래그를 사용하여 ChatGPT 및 Claude와 같은 클라이언트에 원격 MCP로 제공할 수 있습니다.
설정에는 Node.js와 브라우저를 통한 Google 계정 로그인이 필요합니다. 시스템은 OS 키링을 사용하여 자격 증명을 안전하게 관리합니다. 연결되면 특정 폴더를 선택하여 동기화하고 로컬 검색 데이터베이스를 생성할 수 있습니다. 이 MCP server는 검색, 읽기, 쓰기를 위한 세 가지 주요 MCP 도구를 제공합니다. 또한 e5-small과 같은 선택 사항인 로컬 임베딩 모델을 통해 시맨틱 검색을 지원하며, 이를 통해 표준 키워드 매칭보다 더 정교한 문서 검색이 가능합니다.
활용 사례
- 1Google Drive 폴더 동기화AI agent가 특정 Google Drive 폴더를 로컬 Markdown 스냅샷으로 가져와 더 쉽게 처리할 수 있습니다.
- 2시맨틱 문서 검색 수행개발자가 AI에게 단순한 단어 일치가 아닌 시맨틱 검색을 사용하여 정보를 찾도록 지시할 수 있습니다.
- 3문서 지식 관리AI에게 특정 사실, 메모 또는 기억을 문서에 첨부하여 컨텍스트를 유지하도록 요청할 수 있습니다.
- 4웹 클라이언트에 도구 제공사용자가 MCP server를 원격으로 호스팅하여 브라우저 기반 AI 도구가 Drive 데이터에 액세스할 수 있도록 할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
WireCat Google Drive MCP 설치 방법
형식 확인: 2026년 11월 10일Claude Code에 WireCat Google Drive MCP 설치
$ claude mcp add drive-cli -- npx -y @wirecat/drive-cliCursor에 WireCat Google Drive MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"drive-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/drive-cli"
]
}
}
}VS Code에 WireCat Google Drive MCP 설치
.vscode/mcp.json
{
"servers": {
"drive-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wirecat/drive-cli"
]
}
}
}Claude Desktop에 WireCat Google Drive MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"drive-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/drive-cli"
]
}
}
}Codex에 WireCat Google Drive MCP 설치
~/.codex/config.toml
[mcp_servers.drive-cli] command = "npx" args = ["-y", "@wirecat/drive-cli"]
Gemini CLI에 WireCat Google Drive MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"drive-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/drive-cli"
]
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능wirecatlabs/drive-cli is public and reachablegithub.com/wirecatlabs/drive-cli ↗통과
- 패키지가 이 저장소를 소스로 지정@wirecat/drive-cli names wirecatlabs/drive-cli as sourcenpmjs.com/package/@wirecat/drive-cli ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @wirecat/drive-clinpmjs.com/package/@wirecat/drive-cli/v/0.68.0#provenance ↗통과
- 오픈 소스 라이선스 (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-13github.com/wirecatlabs/drive-cli ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @wirecat/drive-cli통과
- 패키지와 의존성에 심각한 보안 권고 없음the package checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 endpoint가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기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:
npm install -g @wirecat/drive-cli
drive --version
drive --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:
drive personal session start
drive personal folders add https://drive.google.com/drive/folders/FOLDER_ID
drive 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. account remove --keep-data or --delete-data goes
further: it revokes the sign-in at Google and forgets the profile, and --delete-data also deletes its snapshots.
Search and export
drive personal search 'budget decision' --json
drive personal search 'budget' --exact --json
drive personal documents list --json
drive personal documents show DOC_ID --json
drive personal documents export DOC_ID --output ./document.md
drive personal status --json
drive 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:
drive models download e5-small
drive 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
drive personal sync --limit 200 --json
drive personal folders remove FOLDER_ID
drive 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
drive personal tags add DOC_ID project-budget review
drive personal documents list tag:review
drive personal notes add DOC_ID 'Check the assumptions' --title Review
drive personal identities list DOC_ID
drive personal documents context DOC_ID
drive personal facts add DOC_ID 'Budget approved for Q4' --type decision --scope work
drive personal memories add DOC_ID 'Q4 budget, in short' --scope work --kind summary
drive personal memories extract DOC_ID --scope work
drive personal documents history DOC_ID
drive 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.
WireCat Google Drive MCP 질문
WireCat Google Drive MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add drive-cli -- npx -y @wirecat/drive-cli를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
WireCat Google Drive MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
지원되는 파일 형식은 무엇인가요?
이 MCP server는 Google Docs, Sheets, PDF, docx, xlsx, CSV, TSV 및 업로드된 Markdown 또는 TXT 파일을 지원합니다.
브라우저의 Claude 또는 ChatGPT에서 어떻게 사용하나요?
--http 플래그를 사용하여 브라우저의 ChatGPT 및 Claude에 MCP 도구를 제공할 수 있습니다.
시맨틱 검색을 지원하나요?
네, 별도로 다운로드 가능한 공유 로컬 텍스트 모델을 사용하여 시맨틱 검색을 수행합니다.
에이전트의 권한을 읽기 전용으로 제한할 수 있나요?
네, DRIVE_READ_ONLY=1 환경 변수를 설정하면 모든 변경 요청을 거부합니다.