Gmail MCP server

Last verified: 2026-09

Read and draft Gmail.

Community Chat, mail & docs Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code

What it does

GongRzhe Gmail AutoAuth MCP. Send, draft, read, search, labels, filters, batch modify/delete. OAuth to a Google account. This is a mail client, not a notifier.

It sits in Chat, mail & docs: These servers act as the bot or the integration you install.

Good for

Search a dedicated mailbox for an invoice thread.
Draft a reply you send yourself from the Gmail UI.
List labels and apply one you already use.
Never connect your primary mail on the first try.

Tools

send_email / draft_email — Outbound.
read_email / search_emails / download_attachment — Inbound.
modify_email / delete_email / batch_modify_emails / batch_delete_emails — Mutate mail.
list_email_labels / create_label / create_filter / list_filters — Labels and filters.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OS	Config file
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json` (usually `C:\Users\<you>\AppData\Roaming\Claude\`)
Linux	`~/.config/Claude/claude_desktop_config.json`

Cursor

Scope	macOS / Linux	Windows
This project	`.cursor/mcp.json` in the repo root
This user	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`

Windsurf

OS	Config file
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

{
  "mcpServers": {
    "gmail": {
      "command": "npx",
      "args": [
        "-y",
        "@gongrzhe/server-gmail-autoauth-mcp"
      ],
      "env": {
        "GMAIL_OAUTH_CLIENT": "from Google Cloud"
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y @gongrzhe/server-gmail-autoauth-mcp

Secrets it wants: Google OAuth

Source repo →

How to get started

Create a Google Cloud OAuth desktop client with Gmail scopes. Complete the browser consent.
Start with read/search only if the package lets you disable send.
Use a dedicated mailbox. Do not connect your primary mail on the first try.

Access risk

send_email and batch_delete_emails are the whole account. Phishing plus this server is a bad mix.

When to skip it

Skip it if you only needed Calendar, or if mail should stay in a human inbox.

Instead: Google Calendar, Slack, Notion.

Chat, mail & docsGoogle CalendarList and create calendar events. OfficialSlackRead channels and post messages. Chat, mail & docsNotionSearch and update Notion pages.

Vs alternatives

Server	Official?	Needs a secret?	Best for
Gmail	No	Yes	Read and draft Gmail.
Google Calendar	No	Yes	List and create calendar events.
Slack	Yes	Yes	Read channels and post messages.
Notion	No	Yes	Search and update Notion pages.

More in Chat, mail & docs

OfficialGoogle MapsGeocode and place search via Google Maps. OfficialSlackRead channels and post messages. Chat, mail & docsAsanaTasks and projects in Asana. Chat, mail & docsConfluenceRead Confluence pages.

All 18 in this category →

FAQ

Why is this high risk?

Mail is identity, password resets, and invoices. send_email and batch_delete_emails are the whole account.

What Google setup?

OAuth desktop client with Gmail scopes. Complete browser consent. Prefer a dedicated mailbox.

Gmail or Calendar?

Different scopes. Install Calendar alone if you only needed events.

Can I disable send?

If the package lets you omit those tools, do. Otherwise assume send is on.