In early 2026, Google launched an official remote MCP server for Gmail: a hosted endpoint at gmailmcp.googleapis.com that AI applications like Claude can call to interact with your Gmail inbox. It is a real, functional product — Google-backed, OAuth-secured, and already listed in Google's developer documentation. It is also a first version, with a tool set that covers read and label operations but stops well short of the actions most people actually want to take on their inbox.
This is an honest breakdown of what it does, where it ends, and how to decide if it fits your workflow.
The 10 Tools Google Exposes
The Gmail MCP server ships with exactly 10 tools:
search_threads— search your inbox using a query string (same syntax as Gmail search). Returns thread IDs and message snippets, sender, subject, and recipients. Does not return full message bodies.get_thread— retrieve the full content of a specific thread including all message bodies.list_drafts— list draft emails with optional query filter and pagination.create_draft— create a new draft email (to, subject, body). Does not send it.list_labels— list all user-defined labels. System labels (INBOX, TRASH, SPAM, UNREAD, etc.) are not returned but can be used by ID in other tools.create_label— create a new label.label_thread— apply one or more labels to an entire thread.unlabel_thread— remove labels from an entire thread.label_message— apply labels to a single message.unlabel_message— remove labels from a single message.
That is the complete list as of the Developer Preview launch. No send. No archive. No delete. No move. No mark-read. No attachment handling. No bulk operations.
What You Can Do With These Tools
The 10 tools cover a useful read-and-organize slice of Gmail. You can build a Claude prompt that searches for threads matching a pattern, reads the content, and applies labels accordingly. You can have Claude draft responses that you review and send yourself from the Gmail interface. You can organize threads into label-based categories — the equivalent of folders — and list or remove those labels programmatically.
For a read-heavy research agent ("what did the sales team send me about Q2?"), or a lightweight organization workflow ("label everything from our vendor as Vendor/Acme"), the tools are functional and accurate.
What You Cannot Do
The gaps are significant for anyone whose goal is inbox action rather than inbox reading.
No send. create_draft queues a message in Drafts but nothing in the tool list sends it. If you want Claude to reply to an email, you get a draft in your Drafts folder. You have to open Gmail and send it yourself.
No archive or delete. There is no archive_thread, trash_message, or delete_message tool. You can technically simulate archive by calling unlabel_message with the INBOX label ID, but this is not an explicit tool, it is a workaround, and there is no bulk version of it.
No mark read or unread. The UNREAD label can be manipulated via label_message and unlabel_message, but there is no dedicated mark-read tool, which means any workflow relying on this needs to handle the label ID lookup separately.
No bulk operations. Every tool operates on a single thread or message. A cleanup that archives 500 newsletters means 500 individual unlabel_message calls. There is no batch endpoint.
No attachment access. You can read message text but cannot list, download, or interact with attachments.
Gmail only. The server is a Gmail product. Outlook, iCloud, Yahoo, Fastmail, IMAP accounts — none of these are in scope.
The Setup: Six Steps Before You Start
Connecting Google's Gmail MCP to Claude is not plug-and-play. The process requires a Google Cloud project and several configuration steps:
- Create a Google Cloud project at console.cloud.google.com
- Enable the Gmail API (
gmail.googleapis.com) in that project - Enable the Gmail MCP API (
gmailmcp.googleapis.com) — a separate service - Configure an OAuth consent screen: app name, audience, and add two scopes manually (
gmail.readonlyandgmail.compose) - Create OAuth 2.0 credentials (Web application type), adding
https://claude.ai/api/mcp/auth_callbackas an authorized redirect URI - Add the server as a custom connector in Claude settings with the server URL and your OAuth credentials
Most users report 15–30 minutes for first-time setup. It also requires a Claude Enterprise, Pro, Max, or Team plan — custom MCP connectors are not available on Claude's free tier.
Who This Is Actually Right For
Google's Gmail MCP makes sense in a specific context: you are a developer building a read-oriented Gmail agent, you want no external dependencies, you are comfortable with GCP, and you have a paid Claude plan already.
The server is Google-maintained, which means you do not need to trust a third party with your OAuth credentials. The endpoint is hosted by Google infrastructure. For developers who want provenance guarantees and minimal external surface area, this matters.
It is also the right default for Gemini CLI workflows — the setup path Google documents first is for Gemini, and the tool set fits the kind of simple "search, read, and draft" prompts that show up in agentic coding workflows.
Where It Falls Short for Real Inbox Management
If your goal is to actually act on your inbox — clean up years of accumulated newsletters, bulk-archive old threads, delete promotional mail, unsubscribe from lists, or run a sweep that classifies and reports on your sender landscape — the 10-tool set does not get you there. Read and label operations are a foundation, not a complete inbox management solution.
For Outlook, iCloud, or any non-Gmail inbox, there is no path with this server at all.
Connect My Email covers the execution layer the Gmail MCP leaves out: send, reply, archive, trash, delete, bulk cleanup, sweep scanning up to 500k messages, RFC 8058 unsubscribe, attachment handling, and multi-provider support across Gmail, Outlook, iCloud, Yahoo, Fastmail, and any IMAP account. It also takes 60 seconds to set up — sign in with Google or Microsoft, paste the MCP URL into Claude, done. No GCP project required, works with any Claude plan including free.
What to Watch For
Google's Gmail MCP is in Developer Preview, which means the tool set can and likely will expand. A send_message tool would be the most consequential addition — it would close the biggest gap immediately. Watch Google's Gmail API release notes for tool additions.
The server is free to use (subject to Gmail API quotas), but the Claude plan requirement means it is not actually free for most users in practice.
The Honest Verdict
Google's Gmail MCP is a real, working, well-documented MCP server with a conservative first-version tool set. It is the right choice if you want Google-backed infrastructure for a read-and-organize Gmail agent and you are comfortable with GCP setup. It is not the right choice if you want to actually clean your inbox, need Outlook or IMAP support, or want more than 10 tools.
The market for Gmail MCP tools is moving fast. Google has a credible position at the foundation layer. The action layer — cleanup, send, bulk operations, multi-provider — is still wide open.
For a direct comparison of the Gmail MCP server against Connect My Email, see the Gmail MCP alternative page. To connect your inbox in 60 seconds, start free or review the full tool list.