Gmail API를 통해 AI agent가 이메일을 검색, 읽기, 초안 관리 및 첨부 파일을 직접 처리할 수 있도록 지원합니다.
다른 이름 dremok/gmail-agent
- 스타
- 1
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.3.1
- 마지막 커밋
- 2026년 10월 11일
- 라이선스
- MIT
gmail-agent MCP란?
Gmail API를 통해 AI agent가 이메일을 검색, 읽기, 초안 관리 및 첨부 파일을 직접 처리할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
gmail-agent MCP server 정보
gmail-agent는 AI agent를 통해 이메일 통신과 파일 첨부를 관리할 수 있게 해줍니다. 이 도구는 개발자가 Claude Desktop, Claude Code 또는 Cursor와 같은 LLM 클라이언트를 Gmail API를 사용하여 자신의 Gmail 계정에 직접 연결할 수 있는 방법을 제공합니다. CLI 또는 stdio를 통한 MCP server 방식으로 로컬 머신에서 작동하며, 제3자 서버 대신 사용자의 Google Cloud OAuth client를 사용하므로 데이터 프라이버시를 보장합니다.
사용자는 Gmail 구문을 사용한 메시지 검색, 스레드를 일반 텍스트로 읽기, 초안 관리 등 광범위한 작업을 수행할 수 있습니다. 특히 첨부 파일 처리 기능이 뛰어납니다. 기존 파일을 덮어쓰지 않고 로컬 디스크로 파일을 다운로드할 수 있으며, PDF나 텍스트 첨부 파일의 경우 파일을 저장하지 않고도 텍스트를 추출할 수 있습니다. 이 server는 사용자의 Google OAuth 권한을 준수하므로, 읽기 전용 또는 전체 수정 권한 등 부여된 액세스 수준에 따라 사용 가능한 도구가 자동으로 결정됩니다.
활용 사례
- 1송장 자동 수집최근 이메일에서 특정 재무 문서를 찾아 로컬 머신으로 다운로드합니다.
- 2이메일 스레드 관리적절한 스레드 헤더를 유지하면서 이메일 스레드의 초안 작성, 전송 또는 답장을 수행합니다.
- 3첨부 파일 내용 추출PDF 첨부 파일의 내용을 디스크에 먼저 저장할 필요 없이 AI 컨텍스트 내에서 직접 읽습니다.
- 4안전한 이메일 초안 작성이메일이 실제로 전송되기 전에 정확한 내용과 MIME 구조를 검토합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
gmail-agent MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 gmail-agent MCP 설치
$ claude mcp add gmail-agent -- uvx gmail-agentCursor에 gmail-agent MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"gmail-agent": {
"command": "uvx",
"args": [
"gmail-agent"
]
}
}
}VS Code에 gmail-agent MCP 설치
.vscode/mcp.json
{
"servers": {
"gmail-agent": {
"type": "stdio",
"command": "uvx",
"args": [
"gmail-agent"
]
}
}
}VS Code CLI에 gmail-agent MCP 설치
$ code --add-mcp '{"name":"gmail-agent","type":"stdio","command":"uvx","args":["gmail-agent"]}'Claude Desktop에 gmail-agent MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"gmail-agent": {
"command": "uvx",
"args": [
"gmail-agent"
]
}
}
}Codex에 gmail-agent MCP 설치
$ codex mcp add gmail-agent -- uvx gmail-agentCodex config.toml에 gmail-agent MCP 설치
~/.codex/config.toml
[mcp_servers.gmail-agent] command = "uvx" args = ["gmail-agent"]
Gemini CLI에 gmail-agent MCP 설치
$ gemini mcp add -s user gmail-agent uvx -- gmail-agentGemini settings.json에 gmail-agent MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"gmail-agent": {
"command": "uvx",
"args": [
"gmail-agent"
]
}
}
}구성
GMAIL_AGENT_ALLOWED_DIRSExtra folders, besides ~/Downloads, the tools may save attachments to and attach files from (separated by :)
GMAIL_AGENT_CONFIG_DIRConfig dir with credentials.json and token (default ~/.config/gmail-agent)
| 이름 | 설명 | 유형 |
|---|---|---|
| GMAIL_AGENT_ALLOWED_DIRS | Extra folders, besides ~/Downloads, the tools may save attachments to and attach files from (separated by :) | |
| GMAIL_AGENT_CONFIG_DIR | Config dir with credentials.json and token (default ~/.config/gmail-agent) |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능dremok/gmail-agent is public and reachablegithub.com/dremok/gmail-agent ↗통과
- 패키지가 이 저장소를 소스로 명시gmail-agent names dremok/gmail-agent as sourcepypi.org/project/gmail-agent/ ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for gmail-agentpypi.org/project/gmail-agent/ ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-11github.com/dremok/gmail-agent ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from gmail-agent통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음49 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기gmail-agent
Gmail for AI agents and the people who run them: search, read, download attachments, send, reply, forward, drafts, labels and trash.
gmail-agent is one small Python package with two faces:
- a CLI for agents that have a shell (Claude Code, Codex, Aider, your own scripts), with
--jsonoutput - an MCP server over stdio for clients like Claude Desktop and Claude Code
It talks directly to the Gmail API from your machine using your own Google Cloud OAuth client, so there is no third-party server in between. You choose how much access it gets when you log in, from read-only up to full.
Why another one? A lot of real agent work with mail is about attachments: find last quarter's invoices, save them, read the PDFs. The hosted Gmail connectors can't save files to disk, and the most used open-source Gmail MCP server is archived. gmail-agent handles attachments well, shows you any write before it happens, and only offers the tools your login allows. See How it compares.
What it does
Read
- Search with Gmail syntax (
from:,has:attachment,filename:pdf,newer_than:30d, ...), paginated - Read a message or a whole thread as plain text (HTML mail is converted)
- List labels and drafts
Attachments
- List a message's attachments with name, type, size and part id
- Download from one message, or every attachment from every message matching a query
- Extract text from PDF and text attachments without saving them
Downloads never overwrite anything. If invoice.pdf exists, the next one becomes invoice_1.pdf, and you get the real paths back. Names are sanitized, so a file called ../../.ssh/config lands as config inside the folder you picked.
Write
- Send new mail with attachments, Cc/Bcc, plain text or HTML
- Reply and reply-all in the same thread (In-Reply-To, References and thread id are set, the original is quoted)
- Forward, including the original attachments
- Drafts: create, list, show, update, send, delete
- Labels: create, rename, delete, add to and remove from messages or threads
- Mark read or unread, star, archive
- Trash and untrash; permanent delete behind an explicit flag
Every write command takes --dry-run, which prints the exact API request and, for mail, the MIME message without changing anything. With --json, results include the ids of whatever was sent or created.
Quick start
You need uv (or pipx) and Python 3.11+.
uv tool install gmail-agent # or: pipx install gmail-agent
For the latest unreleased changes: uv tool install git+https://github.com/dremok/gmail-agent.
Then set it up once (about 5 minutes, guided):
gmail-agent setup # Google Cloud project, OAuth client and login; default access level is "modify"
gmail-agent status # shows the logged-in account and access level
gmail-agent search "has:attachment newer_than:7d"
Then connect your agent. In Claude Code: /plugin install gmail-agent --marketplace dremok/gmail-agent. For Codex, Gemini CLI, VS Code, Cursor and Claude Desktop, see MCP server.
How it compares
Checked against each project's source and docs in October 2026. Corrections are welcome as issues.
| gmail-agent | Claude's Gmail connector | google_workspace_mcp | GongRzhe Gmail-MCP-Server | |
|---|---|---|---|---|
| Setup | Your own OAuth client; gmail-agent setup guides you (about 5 minutes) |
One click | Your own OAuth client, by hand | Your own OAuth client, by hand |
| Runs as | CLI and stdio MCP, on your machine | Hosted (web, desktop, mobile) | stdio or HTTP, multi-user | stdio MCP |
| Save attachments to disk | Yes, never overwrites | No | Yes, to its own folder, deleted after an hour | Yes, overwrites files with the same name |
| Every attachment matching a search | Yes | No | No | No |
| Text of PDF attachments | Yes | No | No | No |
| Forward with original attachments | Yes | Not documented | Yes | No forward |
| Drafts | Create, update, send, delete | Yes | Create only | Create only |
| Dry run of every write, with the MIME message | Yes | No, asks before each write instead | No | No |
| Read-only mode | Yes | No, the grant includes sending | Yes | No |
| Tool list follows the granted scope | Yes | No | From server flags | No |
| Permanent delete | Only with --allow-delete and a full login |
Not offered | Not offered | Offered without a guard |
| Drive, Calendar, Docs | No, Gmail only | Separate connectors | Yes | No |
| Maintained | Yes | Yes | Yes | Archived in 2025 |
Use something else if:
- You want no setup, or use Claude on the web or your phone. The built-in connector is one click away.
- You need Drive, Calendar and Docs in the same server, or one server for a team over HTTP. google_workspace_mcp covers all of Workspace.
- You need Gmail filters, sending from an alias, your Gmail signature or inline images in outgoing mail. gmail-agent does none of these yet.
- You want a plain CLI for all of Google Workspace. googleworkspace/cli (
gws) is a good one. It dropped its MCP server in version 0.8.0.
Coming from GongRzhe/Gmail-MCP-Server?
That server is archived. Moving takes a few minutes, and you can keep your Google Cloud project.
-
Install:
uv tool install gmail-agent -
Reuse your OAuth client, not your token. Setup checks the client, installs it and logs you in:
gmail-agent setup --client-file ~/.gmail-mcp/gcp-oauth.keys.jsonDo not copy GongRzhe's
credentials.jsonby hand. Despite the name it is your login token, while gmail-agent'scredentials.jsonis the OAuth client, and the token formats differ anyway. gmail-agent needs a Desktop app client. If yours is a Web application client, setup says so; create a Desktop client in the same project and pass that file instead. -
Point your MCP client at gmail-agent. Replace
npx @gongrzhe/server-gmail-autoauth-mcpwithgmail-agent mcp, for exampleclaude mcp add gmail --scope user -- gmail-agent mcp. For Claude Desktop, see MCP server. -
Optional cleanup: revoke the old grant at myaccount.google.com/permissions and remove
~/.gmail-mcp.
| GongRzhe tool | gmail-agent tool | Notes |
|---|---|---|
search_emails |
search_messages |
Adds paging with page_token |
read_email |
get_message, get_thread |
HTML mail comes back as text |
send_email |
send_message, reply_to_message |
Replies set the threading headers for you |
draft_email |
create_draft, or any send tool with as_draft |
Drafts can also be updated and sent |
modify_email, batch_modify_emails |
modify_labels, mark_messages |
Labels by name or id |
delete_email, batch_delete_emails |
trash |
Permanent delete needs mcp --allow-delete and a full login |
list_email_labels |
list_labels |
|
create_label, update_label, delete_label |
create_label, rename_label, delete_label |
No visibility options |
get_or_create_label |
list_labels, then create_label |
|
download_attachment |
download_attachments |
Picks by filename or part id, never overwrites |
download_matching_attachments, read_attachment_text, forward_message |
New | |
create_filter and the other filter tools |
None | gmail-agent never touches settings, filters or forwarding |
Two behaviours differ on purpose: delete means trash unless you opt in, and the tool list shrinks to what your login allows. If tools seem to be missing, check the level with gmail-agent status.
Google Cloud setup
Gmail has no API keys for personal mail, so you create your own OAuth client in Google Cloud. It is free and you do it once. gmail-agent setup walks you through it and does what Google lets it do for you:
- Project and Gmail API. If gcloud is installed and logged in, setup creates a project called
gmail-agent-plus six random characters (it asks first) and enables the Gmail API. Without gcloud it opens the two console pages and asks for the project ID.--project IDuses a project you already have. - Consent screen and publishing. Google has no API for these, so setup opens the pages and tells you what to click: app name
gmail-agent, audience External, then Publish app so the status is In production. Publishing avoids the 7-day login expiry of Testing mode, and you do not have to add yourself as a test user. Google calls the app unverified, which is expected for your own app and fine for personal use (it is capped at 100 users). - Desktop client. Setup opens the Clients page. Create a client of type Desktop app and click Download JSON (Google shows the secret only then). Setup spots the file in
~/Downloads, checks that it is a Desktop client from the right project, and installs it as~/.config/gmail-agent/credentials.json, readable only by you. You can also pass--client-file PATH, or press Ctrl-C and paste the client ID and secret. - Login. A browser opens; pick your account. Google says "Google hasn't verified this app": click Continue and keep all boxes ticked. Setup checks the account and prints
Set up: logged in as you@example.com with modify access.
Run it again whenever you like; it skips what is already done. Options: --scope LEVEL (see Access levels), --no-gcloud, and --no-browser, which prints the links instead of opening them (the login redirect goes to localhost, so the browser must run on the same machine).
Setting up by hand
The same steps without the wizard:
-
Create a project at console.cloud.google.com/projectcreate and make sure it is selected in the top bar.
-
Enable the Gmail API on the Gmail API page.
-
Configure the consent screen in Google Auth Platform: Get started, app name
gmail-agent, your address as support and contact email, audience External, agree, Create. -
Publish the app under Audience (Publish app, status In production). If you would rather stay in Testing mode, add your address under Test users instead, and expect to log in again every 7 days.
-
Create a Desktop client under Clients: Create client, application type Desktop app, Create, and download the JSON from the dialog. If you miss the download, create a new client.
-
Install it, either with
gmail-agent setup --client-file ~/Downloads/client_secret_*.json, which also logs in, or by hand:mkdir -p ~/.config/gmail-agent mv ~/Downloads/client_secret_*.json ~/.config/gmail-agent/credentials.json chmod 600 ~/.config/gmail-agent/credentials.json gmail-agent login # or: gmail-agent login --scope readonly
If something is missing later, the error names the fix: a deleted or expired client points back to gmail-agent setup, a Gmail API that is not enabled comes with the link to enable it, and an expired login says to run gmail-agent login (and to publish the app if it happens every 7 days).
Access levels
Pick one with gmail-agent login --scope LEVEL. To change it later, run login again.
| Level | Google scope | What a token with it can do |
|---|---|---|
readonly |
gmail.readonly |
Read all mail, labels and settings. Cannot change anything. |
compose |
gmail.readonly + gmail.compose |
Read, plus create, change and delete drafts, and send mail. |
modify (default) |
gmail.modify |
Everything except permanent deletion: read, send, drafts, labels, archive, trash. |
full |
https://mail.google.com/ |
Everything, including deleting mail permanently. Also grants IMAP/SMTP-level access. |
If a command needs more than your login has, it stops before calling Gmail and tells you exactly what to run, for example:
error: Sending needs send/draft access, but this login only granted gmail.readonly. Run: gmail-agent login --scope compose
Only use full if you want permanent delete. Trash (available with modify) is emptied by Gmail after 30 days anyway.
CLI usage
Every command takes --json for machine-readable output, before or after the command (gmail-agent --json search ... and gmail-agent search ... --json both work). Run gmail-agent <command> --help for all options.
Read and download
gmail-agent search "from:billing@example.com newer_than:30d"
gmail-agent search "has:attachment filename:pdf" -n 50 --json
gmail-agent search "label:receipts" --page-token <token from the previous page>
gmail-agent message 18c2f0a1b2c3d4e5
gmail-agent thread 18c2f0a1b2c3d4e5
gmail-agent labels
gmail-agent attachments 18c2f0a1b2c3d4e5
gmail-agent download 18c2f0a1b2c3d4e5 -o ~/Downloads/mail # all of them
gmail-agent download 18c2f0a1b2c3d4e5 -o ./out --name invoice.pdf # by filename
gmail-agent download 18c2f0a1b2c3d4e5 -o ./out --name 1.2 # by part id
gmail-agent fetch "subject:invoice after:2026/01/01" -o ./invoices --match "*.pdf"
gmail-agent read 18c2f0a1b2c3d4e5 invoice.pdf # print PDF text
Send, reply, forward
gmail-agent send --to alice@example.com --cc bob@example.com --subject "Report" \
--body "Attached." --attach report.pdf
gmail-agent send --to alice@example.com --subject "News" --html-file news.html
gmail-agent reply 18c2f0a1b2c3d4e5 --body "Thanks, got it."
gmail-agent reply 18c2f0a1b2c3d4e5 --all --body-file answer.txt --no-quote
gmail-agent forward 18c2f0a1b2c3d4e5 --to carol@example.com --body "FYI"
gmail-agent forward 18c2f0a1b2c3d4e5 --to carol@example.com --no-attachments --draft
send, reply and forward send right away. Add --draft to save to Drafts instead, or --dry-run to see what would go out. With --html and no --body, a plain-text version is derived from the HTML. Forwards leave out images that were embedded in the original HTML (logos, signatures); real attachments go along.
Drafts
gmail-agent draft list
gmail-agent draft create --to alice@example.com --subject "Plan" --body "First version"
gmail-agent draft get r-123456789
gmail-agent draft update r-123456789 --body "Second version" --attach notes.pdf
gmail-agent draft send r-123456789
gmail-agent draft delete r-123456789
draft update keeps every field you do not pass, including attachments (use --drop-attachments to clear them) and the thread of a draft reply.
Labels and state
gmail-agent label create "Receipts/2026"
gmail-agent label rename "Receipts/2026" "Receipts/Tax 2026"
gmail-agent label add Receipts 18c2f0a1b2c3d4e5 18c2f0a1b2c3d4e6
gmail-agent label remove Receipts 18c2f0a1b2c3d4e5
gmail-agent label delete "Receipts/Tax 2026"
gmail-agent mark-read 18c2f0a1b2c3d4e5
gmail-agent star 18c2f0a1b2c3d4e5
gmail-agent archive 18c2f0a1b2c3d4e5 --thread # ids are thread ids
gmail-agent trash 18c2f0a1b2c3d4e5
gmail-agent untrash 18c2f0a1b2c3d4e5
gmail-agent delete 18c2f0a1b2c3d4e5 --permanent # needs login --scope full
Labels can be given by name (case-insensitive) or id. The state commands also exist as mark-unread, unstar and unarchive. delete refuses to run without --permanent.
Dry run
$ gmail-agent trash 18c2f0a1b2c3d4e5 --dry-run
Dry run, nothing was changed.
{
"method": "users.messages.trash",
"params": {
"id": "18c2f0a1b2c3d4e5"
}
}
For mail, the dry run also prints the MIME message: every header and body part, with each attachment's contents replaced by its size.
Exit codes: 0 ok, 1 error, 2 a setup step or scope is missing (the message says which).
MCP server
gmail-agent mcp runs an MCP server over stdio. It starts even before you log in; tools then return an error telling the user to run gmail-agent login.
Claude Code plugin (recommended for Claude Code). It adds the MCP server plus a skill that tells Claude when and how to use it: attachments, dry runs before sending, and treating mail as untrusted.
/plugin install gmail-agent --marketplace dremok/gmail-agent
On Claude Code older than 2.1.275, run /plugin marketplace add dremok/gmail-agent, then /plugin install gmail-agent@dremok. The plugin runs the server with uvx, so you need uv. If you also added the server with claude mcp add, remove that entry (claude mcp remove gmail) or you get every tool twice.
Claude Code without the plugin (--scope user here is Claude Code's config scope, not the Gmail access level):
claude mcp add gmail --scope user -- gmail-agent mcp
claude mcp add gmail --scope user -- gmail-agent mcp --read-only # reading tools only
claude mcp add gmail --scope user -- uvx gmail-agent mcp # without installing first
Codex, Gemini CLI and VS Code:
codex mcp add gmail -- uvx gmail-agent mcp
gemini mcp add --scope user gmail uvx gmail-agent mcp
code --add-mcp '{"name":"gmail","command":"uvx","args":["gmail-agent","mcp"]}'
Cursor, Windsurf, Cline and other clients take the usual JSON (for Cursor, in ~/.cursor/mcp.json):
{
"mcpServers": {
"gmail": { "command": "uvx", "args": ["gmail-agent", "mcp"] }
}
}
Claude Desktop: edit claude_desktop_config.json (Settings > Developer > Edit Config). Desktop apps often do not see your shell's PATH, so use the absolute path from which gmail-agent:
{
"mcpServers": {
"gmail": {
"command": "/Users/you/.local/bin/gmail-agent",
"args": ["mcp"]
}
}
}
Without installing first, uvx works too (again with its absolute path, from which uvx): "command": "/Users/you/.local/bin/uvx", "args": ["gmail-agent", "mcp"].
Which tools show up follows the access level in your saved login: readonly gets only the reading tools, compose adds sending and drafts, modify adds labels, state and trash. Before you have logged in, the server offers the modify set, and each tool explains how to log in. After changing the level with gmail-agent login --scope ..., restart the MCP client so it picks up the new tool list.
Server flags: --read-only keeps only the reading tools, whatever the login allows. --allow-delete adds delete_permanently, and only if the login has full access. Without both, the server has no way to delete mail permanently. --allow-dir PATH (repeatable) lets the tools save attachments to and attach files from another folder besides ~/Downloads; see Local files.
For example, to let Claude Code save attachments in a project folder too:
claude mcp add gmail --scope user -- gmail-agent mcp --allow-dir ~/code/my-project
Tools:
| Tool | What it does |
|---|---|
account_status |
Logged-in address, message counts, access level |
search_messages |
Gmail query, paginated; id, thread, date, from, subject, snippet, attachments |
get_message, get_thread |
Headers, plain-text body, attachment list |
list_labels |
System and user labels |
list_attachments |
Attachments of a message with part ids |
download_attachments |
Save all or selected attachments of a message to a folder |
download_matching_attachments |
Save attachments from every message matching a query |
read_attachment_text |
Text of a PDF or text attachment, without saving |
list_drafts, get_draft |
Drafts and their content |
send_message, reply_to_message, forward_message |
Send now, or with as_draft save to Drafts |
create_draft, update_draft, send_draft, delete_draft |
Draft management |
create_label, rename_label, delete_label |
Label management |
modify_labels, mark_messages |
Add/remove labels; read, unread, star, unstar, archive, unarchive |
trash, untrash |
Move to and from Trash |
delete_permanently |
Only with --allow-delete and a full login |
Every write tool takes dry_run. Every tool carries all four MCP hints. Reading tools are readOnlyHint. Sending (send_message, reply_to_message, forward_message, send_draft), update_draft, trash and the delete tools are destructiveHint, because they cannot be taken back or they overwrite or remove something, so clients that confirm destructive calls will ask first. Tools that are safe to repeat, such as mark_messages and trash, are idempotentHint; send_message and the downloads are not.
gmail-agent MCP 질문
gmail-agent MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add gmail-agent -- uvx gmail-agent를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
gmail-agent MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
이 MCP server가 첨부 파일을 로컬 디스크에 저장할 수 있나요?
네, 특정 메시지 또는 쿼리에 일치하는 모든 메시지에서 첨부 파일을 다운로드할 수 있습니다. 중복 파일은 이름을 변경하여 기존 파일을 덮어쓰지 않도록 보장합니다.
보안과 개인정보 보호는 어떻게 처리하나요?
사용자의 Google Cloud OAuth client를 사용하여 로컬 머신에서 Gmail API와 직접 통신하므로 제3자 서버가 개입하지 않습니다.
쓰기 작업을 실행하기 전에 테스트할 수 있나요?
네, 모든 쓰기 명령은 dry-run 모드를 지원합니다. 이 모드에서는 실제 변경을 수행하지 않고 정확한 API 요청과 MIME 메시지를 출력합니다.