Use Claude with Gmail through MCP to search inboxes, summarize threads, draft replies, and save attachments. Start with the safest server choice, copy a working config, and understand the OAuth risk before connecting.
Connect Claude to Gmail with MCP
If your goal is “let Claude read, search, and draft inside Gmail without copy-pasting email threads by hand,” this is the shortest path.
Recommended MCP servers for this use case
| Server | Best for | Not ideal when | Auth | Permission risk |
|---|---|---|---|---|
| MCP GSuite Server | Gmail search, drafting, replying, and attachment handling in one setup | You only need task lists, not email | OAuth2 files + Gmail scopes | High |
| Connect Claude to Google Workspace with MCP | Teams choosing between Gmail, Calendar, and Tasks setup paths | You already know you only need Gmail | Mixed | High |
Quick selection (30 seconds)
- Pick MCP GSuite if Gmail is the main workflow and you may later need Calendar too.
- Do not start with broad Google access if the actual need is only summarizing or drafting from one mailbox.
- Use a test or lower-risk mailbox first if the inbox contains sensitive company or legal communications.
Copy-paste config (Claude Desktop)
{
"mcpServers": {
"mcp-gsuite": {
"command": "uvx",
"args": [
"mcp-gsuite",
"--accounts-file",
"/absolute/path/to/.accounts.json",
"--credentials-dir",
"/absolute/path/to/credentials"
]
}
}
}You will also need a .gauth.json file with your Google OAuth client details and a .accounts.json file listing the Gmail account(s) Claude may use.
Gmail auth checklist
| Item | Required | Sensitive | Notes |
|---|---|---|---|
| Gmail API enabled in Google Cloud | Yes | No | Must be enabled before first login |
.gauth.json | Yes | Yes | Stores OAuth client metadata |
.accounts.json | Yes | Yes | Include only the mailbox accounts you want exposed |
| Credentials directory | Yes | Yes | Refresh-token cache lives here |
| Gmail scope | Yes | Yes | Keep it to mail only if Calendar is unnecessary |
First tool-call prompts
- “Retrieve my latest unread messages and group them by urgency.”
- “Search my inbox for messages from finance this month and summarize outstanding asks.”
- “Draft a reply to the latest email from Alice, but save it as a draft instead of sending.”
Risk and permission notes
- Gmail access exposes highly sensitive data quickly. Start with the narrowest possible account scope.
- Drafting is safer than sending during rollout because you can review outputs before anything leaves the mailbox.
- If you do not need attachments saved locally, avoid workflows that move files out of email by default.
FAQ
What is the best Gmail MCP option in this site right now?
MCP GSuite Server is the strongest current fit because it already covers Gmail search, thread retrieval, drafting, and reply workflows.
Should I grant full mail access on day one?
Only if the workflow truly requires it. Use a test mailbox or a low-risk account first, then expand once the prompts and review process are stable.
How do I reduce rollout risk fastest?
Start with search and summarization only, then move to draft creation, and only later consider actual sending workflows.
Related pages
- MCP GSuite Server details
- Connect Claude to Google Workspace with MCP
- Add MCP Servers to Claude Desktop
Sources and freshness
- Sources: official server pages linked above.
- Updated: March 15, 2026.