gmail-agent

Name: gmail-agent
Author: dremok

by dremokversion 0.3.1i★ –iRuns on your computer

Registry nameio.github.dremok/gmail-agent

Install

Overview

Description from the maker (original English)

Gmail for AI agents: search, read, download attachments, send, reply, drafts, labels.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: GMAIL_AGENT_CONFIG_DIR, GMAIL_AGENT_ALLOWED_DIRS

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "gmail-agent": {
      "command": "uvx",
      "args": [
        "gmail-agent",
        "mcp"
      ],
      "env": {
        "GMAIL_AGENT_CONFIG_DIR": "your-value",
        "GMAIL_AGENT_ALLOWED_DIRS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add gmail-agent --env GMAIL_AGENT_CONFIG_DIR=your-value --env GMAIL_AGENT_ALLOWED_DIRS=your-value -- uvx gmail-agent mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gmail-agent": {
      "command": "uvx",
      "args": [
        "gmail-agent",
        "mcp"
      ],
      "env": {
        "GMAIL_AGENT_CONFIG_DIR": "your-value",
        "GMAIL_AGENT_ALLOWED_DIRS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gmail-agent": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "gmail-agent",
        "mcp"
      ],
      "env": {
        "GMAIL_AGENT_CONFIG_DIR": "your-value",
        "GMAIL_AGENT_ALLOWED_DIRS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

GMAIL_AGENT_CONFIG_DIR env
Config dir with credentials.json and token (default ~/.config/gmail-agent)
GMAIL_AGENT_ALLOWED_DIRS env
Extra folders, besides ~/Downloads, the tools may save attachments to and attach files from (separated by :)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dremok, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Chat & emaili

More stars than 0% of the other 1766 servers in this category
Published to the registry more recently than 50% of the other 1766 servers in this category
Basic checks equal to or better than 100% of the other 1766 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is gmail-agent safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 26 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Vexa, emailmd, MCP WhatsApp Cloud

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Vexa

by Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

Runs in the cloud★ 2,949Apache-2.0Updated 2 months ago

Install

emailmd

by anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

Computer or cloud★ 1,385MITUpdated 31 days ago

Install

MCP WhatsApp Cloud

by codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

Runs on your computer★ 277MITUpdated 5 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 --json output
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.json

Do not copy GongRzhe's credentials.json by hand. Despite the name it is your login token, while gmail-agent's credentials.json is 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-mcp with gmail-agent mcp, for example claude 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 ID uses 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

Only the beginning is shown; read the rest in the repo

gmail-agent

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Chat & emaili

Common questions

Alternatives

Vexa

emailmd

MCP WhatsApp Cloud

README from the maker

gmail-agent

What it does

Quick start

How it compares

Coming from GongRzhe/Gmail-MCP-Server?

Google Cloud setup

Setting up by hand