Reads and organizes your inbox, and leaves the sending to you.

A fit for working through mail while keeping sending in your own hands: as of October 2026 it has no tool that sends mail, so each reply it writes waits in your Drafts folder.

What it is

A remote MCP server Google runs at gmailmcp.googleapis.com. It acts with your Google account's own permissions. It is part of the Google Workspace Developer Preview Program, which gives early access to features.

What you get

Mail threads searched with a query, and any thread or message read in full
Draft emails written to your Drafts folder, with to, cc and bcc, and existing drafts listed or opened
Labels listed, created (including nested ones like Projects/Alpha) and added to or removed from threads and messages
Threads and messages moved to Trash or Spam, and brought back
A link with each result to open it in Gmail on the web

Requirements

A Google account in the Google Workspace Developer Preview Program, and a Google Cloud project with the Gmail API and the Gmail MCP service turned on.
You set up an OAuth consent screen and create your own OAuth client ID and secret in that project, then enter them in your MCP client.
In Claude.ai or Claude Desktop this is a custom connector, which needs a Pro, Max, Team or Enterprise plan.
Google's guide adds only the gmail.readonly and gmail.compose scopes to the consent screen; add gmail.modify if you want it to label mail or move it to Trash or Spam.
Google warns that emails from strangers can carry hidden instructions, so review what your agent does on your behalf.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen