gmail-tool
Search, inspect, label, and back up Gmail from the terminal with guided OAuth setup, shell-friendly output, and reusable Gmail queries.
gmail-tool is built for fast mailbox exploration and repeatable command-line workflows. It works well for personal Gmail usage, local automation, and Google Workspace environments that need service account access.
Features
- List Gmail labels
- Read full messages by Gmail message ID
- Search Gmail with raw Gmail search operators
- Reuse saved queries from
config.toml - Run actions against either labels or search results:
list,count,delete,backup,label-add --name <label_name>, andlabel-remove --name <label_name> - Export labels and message lists as
jsonorcsv - Filter message results with
--from-date,--to-date, and--starred true|false - Back up matching messages as resumable
.emlfiles - Optionally move successfully backed-up messages to Gmail Bin with
--deleteand--force - Use guided auth helpers including
gmail-tool auth login,gmail-tool auth check,gmail-tool auth paths,gmail-tool auth logout, andgmail-tool auth login --no-browser - Use OAuth desktop flow without requiring
config.toml - Use service account auth for Google Workspace domain-wide delegation
Installation
gmail-tool requires Python 3.12+.
pip
python -m pip install gmail-tool
Verify the install:
gmail-tool --version
Homebrew
brew install joelee/oss/gmail-tool
Verify the install:
gmail-tool --version
Quick Start
For normal OAuth usage, config.toml is optional.
- In Google Cloud Console, create a Desktop OAuth client and enable the Gmail API.
- Save the downloaded client JSON to
~/.config/gmail-tool/client_secret.json. - Authenticate and verify access:
gmail-tool auth login
gmail-tool auth check
gmail-tool labels
If you are on a remote shell or headless machine, use gmail-tool auth login --no-browser.
- Run a real query:
gmail-tool search from:bob@example.com has:attachment
Full credential setup steps are in Google Credentials.
Authentication
Supported auth modes:
- OAuth desktop flow
- Service account flow for Google Workspace domain-wide delegation
For the normal OAuth desktop flow, config.toml is optional.
Quick start:
- Place your Desktop OAuth client JSON at
~/.config/gmail-tool/client_secret.json - Run
gmail-tool auth login - Run
gmail-tool auth check
Useful helpers:
gmail-tool auth pathsgmail-tool auth logoutgmail-tool auth login --no-browser
Default OAuth file locations when no overrides are set:
- client secret:
${XDG_CONFIG_HOME:-~/.config}/gmail-tool/client_secret.json - token:
${XDG_STATE_HOME:-~/.local/state}/gmail-tool/oauth-token.json
Credential setup instructions are in Google Credentials.
Common Commands
Show the CLI version:
gmail-tool --version
Enable debug output to stderr:
gmail-tool --verbose labels
List labels as JSON:
gmail-tool labels -f json
Auth diagnostics:
gmail-tool auth check
Read a full message by identifier:
gmail-tool message read <MESSAGE_ID>
Move a message to Bin:
gmail-tool message delete <MESSAGE_ID>
gmail-tool message delete <MESSAGE_ID> --force
Search with a raw Gmail query:
gmail-tool search from:bob@example.com has:attachment
Count search matches:
gmail-tool search -a count from:bob@example.com
Add a label to all search matches:
gmail-tool search -a label-add --name FollowUp from:bob@example.com
List built-in search examples:
gmail-tool search --list-query-examples
Print a Gmail search operator cheat sheet:
gmail-tool search --cheat-sheet
Run a saved query from config.toml:
gmail-tool search --saved-query recent_attachments
Back up matching messages as .eml files:
gmail-tool search -a backup from:bob@example.com
gmail-tool search -a backup --backup-path /tmp/gmail-backups from:bob@example.com
gmail-tool search -a backup --backup-path /tmp/gmail-backups --delete from:bob@example.com
gmail-tool search -a backup --backup-path /tmp/gmail-backups --delete --force from:bob@example.com
Count messages in a label:
gmail-tool label INBOX -a count
gmail-tool label <LABEL> accepts either an exact Gmail label name such as @Later or an exact label ID such as Label_66.
List messages in a label:
gmail-tool label IMPORTANT -l 10 --starred true
Or export them as CSV:
gmail-tool label IMPORTANT -l 10 -f csv
Plain-text list output includes message_id values that can be passed to message read.
The search command returns the same message list structure as label ... list.
Both label and search default to the list action. Use --action or -a to switch to count, delete, backup, label-add --name <name>, or label-remove --name <name>.
List supported actions:
gmail-tool label --list-actions
gmail-tool search --list-actions
gmail-tool search --help-action backup
gmail-tool label --help-action label-add
Configuration
See config.toml, .env.sample, and Configuration.
All commands accept --config <path> or -c <path>. If omitted, config discovery falls back through environment, XDG, home config, /etc, and the project directory. If no config file is found, built-in OAuth defaults are used.
Development
uv sync --dev
uv run pytest --cov=src/gmail_tool --cov-report=term-missing --cov-report=xml --cov-report=json
./scripts/update-coverage-badge.sh coverage.json
uv run pre-commit run --all-files
Coverage artifacts produced by CI:
coverage.jsoncoverage.xml.github/badges/coverage.json
Releases
PyPI publishing is handled by the GitHub Actions Publish workflow on version tags such as v0.2.2.
Release packaging steps are documented in Release Packaging.
Homebrew packaging steps are documented in Homebrew Packaging.
Live Gmail Integration Tests
Live Gmail tests are opt-in and use your local .env and config.toml.
Run them with an existing OAuth token:
ENABLE_LIVE_GMAIL_TESTS=true uv run pytest -m live_gmail
If this is your first OAuth run and no token exists yet, allow browser authentication explicitly:
ENABLE_LIVE_GMAIL_TESTS=true ALLOW_GMAIL_OAUTH_BROWSER=true uv run pytest -m live_gmail -s
These tests verify Gmail API access against your real mailbox and are skipped unless explicitly enabled.
Documentation
Metadata
Release files for gmail-tool 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gmail_tool-0.3.1.tar.gz | 18.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gmail_tool-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.8 kB
Release files / gmail_tool-0.3.1.tar.gz
| Download URL | gmail_tool-0.3.1.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bc59823aab8d34487020b5b718459e099657571441f8f35e40cfc1603ff89b5
|
|
BLAKE2b-256 checksum How to use checksums |
90058ccb95b16c7e3ce2c1ed6900337996d034d681ceb1c50d58a58cc37170cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logRelease files / gmail_tool-0.3.1-py3-none-any.whl
| Download URL | gmail_tool-0.3.1-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e732d5bbade6bc6fdf1a2af6927143647ffb03a80f41ed5cdcf3970561e39901
|
|
BLAKE2b-256 checksum How to use checksums |
ad503edb3b1e4ce90979f46454346c2e133b3935ab2fce609358be6f008b2afb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logSecurity for gmail-tool 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gmail_tool-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.