--- title: "Gmail MCP: What Google's Workspace MCP Servers Do, and What a Shared Inbox Needs" description: "Gmail MCP lets Claude, ChatGPT or Gemini search, read and draft email. What Google's official server does, where it stops, and what a shared inbox needs." author: "Cody Duval" url: https://www.keeping.com/content/google-workspace-mcp/ datePublished: 2026-11-03 --- # Gmail MCP: What Google's Workspace MCP Servers Do, and What a Shared Inbox Needs > **The short answer:** Gmail MCP is how an AI assistant like Claude, ChatGPT or Gemini searches, reads and drafts email in Gmail. Google's official Gmail MCP server is a developer preview that needs a Google Cloud project, and it searches, reads, labels and drafts but doesn't send. It and the assistants' built-in Gmail connections all act as the one person who signed in, so none of them can assign or track a shared support@ inbox. For that, connect your assistant to your shared inbox's own MCP server. Gmail MCP is how an AI assistant like Claude, ChatGPT or Gemini searches, reads and drafts email in Gmail. Google’s official Gmail MCP server does that through your own Google account, and it can add labels too. It’s part of Google’s Workspace Developer Preview, needs your own Google Cloud project and OAuth client, and has no send tool. Like the Gmail connections built into Claude, ChatGPT and Gemini, it works on one person’s mailbox through that person’s account. So it can’t assign, track or report on a shared support@ inbox. This guide is for teams answering support@ from Google Workspace who want to know what each option reaches, and what to use when the answer is “only my own mail.” ## What is a Gmail MCP server? A Gmail MCP server is a connection that turns Gmail actions, like searching threads, reading a message, adding a label or writing a draft, into tools an AI assistant can call. MCP (Model Context Protocol) is the open standard behind it. You sign in once, and the assistant uses those tools when you ask for something in plain language. Ask “find the invoice thread from Acme last week and draft a reply,” and the assistant picks the search tool, then the read tool, then the draft tool. You never see an API. Servers come in two kinds. A remote server runs on the provider’s side and you connect it by URL, which is how Google’s Gmail server works. A local server runs on your own computer, usually an open-source project you install and configure with your own credentials. ## Google’s official Google Workspace MCP servers Google hosts remote MCP servers for Gmail, Drive, Docs, Sheets, Slides, Calendar, Chat, the People API and Classroom. Google lists them as part of the Google Workspace Developer Preview Program, which gives early access to features that aren’t generally released. Each server has its own endpoint, and you connect only the ones you need. ### What the Gmail MCP server can do Google’s Gmail MCP reference lists tools in four groups: - **Search:** find threads with Gmail search queries - **Read:** get a single message or a whole thread - **Labels:** list labels, and add or remove a label on a message or thread - **Drafts:** create a draft and list existing drafts There’s no tool to send, delete, archive or mark spam. A draft lands in your Gmail drafts folder, and you send it yourself. The server asks for two Gmail scopes: read-only access and compose, which covers drafts. ### How to get Google’s Gmail MCP server The setup is aimed at developers and admins, and it takes some time in Google Cloud: 1. Join the Google Workspace Developer Preview Program with your Workspace account. 2. Create a Google Cloud project, and enable the Gmail API and the Gmail MCP API in it. 3. Set up the OAuth consent screen with the Gmail scopes. 4. Create a web application OAuth client and mark it as a client for an AI-powered agent. 5. Add the server to your assistant: Google names Claude (as a custom connector on a Claude Pro, Max, Team or Enterprise plan) and its own Antigravity, and any client that supports remote MCP servers can use it. Google’s [Workspace MCP setup guide](https://developers.google.com/workspace/guides/configure-mcp-servers) has the exact steps. It also carries a clear warning about indirect prompt injection: an email can contain hidden instructions that try to hijack your assistant, so use trusted tools and review what the assistant does for you. ## Gmail in Claude, ChatGPT and Gemini without setting up a server You don’t need Google’s server to get Gmail into your assistant. Claude, ChatGPT and Gemini each have their own Gmail connection that you turn on from the assistant’s settings, with no Cloud project. Each one connects a single Google account, and each does slightly different things. **Claude’s Gmail connector** can search and read email, draft, send, reply and forward, and manage labels and threads. It sees attachment details but not their contents. By default, Claude asks for your approval before each of those actions. On Claude Team and Enterprise, an Owner enables the connector first, and a Google Workspace admin may need to mark Claude as a trusted app. Anthropic’s [Google Workspace connectors guide](https://support.claude.com/en/articles/10166901-use-google-workspace-connectors) says Claude can only reach the data of the Google account you connected. **ChatGPT’s Gmail plugin** searches your mail and helps you prepare replies from it. In a ChatGPT workspace, write actions for an app stay off until an admin turns them on. **The Gemini app** can find and summarize information from Gmail. On a work or school account it can’t create an email draft or delete email, according to Google’s [Gemini connected apps help](https://support.google.com/gemini/answer/14959807), and it needs a qualifying Workspace edition, Keep Activity turned on, and an admin who allows connected apps. That’s the Gemini app, which is separate from [using Gemini in Gmail for customer support](https://www.keeping.com/content/gemini-customer-support-gmail/) through Help me write and the side panel. ## Community and third-party Gmail MCP servers There are also dozens of open-source Gmail MCP servers, plus automation platforms that wrap Gmail as one of many apps. Many can do more than Google’s server, including sending, deleting and filtering mail. The trade-off is ownership. You run the server or trust the platform, you create the Google OAuth credentials, and you’re responsible for where your email goes and what the assistant is allowed to do with it. Every one of them still signs in as a single Gmail user. ## Gmail MCP options compared Here’s how each option answers the question that matters for a team: whose mailbox does it see? | Option | Setup | Whose mailbox | Sends email? | Assignment, status, notes | | --- | --- | --- | --- | --- | | Google’s Gmail MCP server | Developer preview, Cloud project, OAuth client | The person who signed in | No, drafts only | No | | Claude’s Gmail connector | Turn on in Claude | The one Google account you connected | Yes, with approval | No | | ChatGPT’s Gmail plugin | Turn on in ChatGPT | The Google account you connected | Depends on admin settings | No | | Gemini app | Turn on in Gemini | Your own account | No drafts on work accounts | No | | Community servers | Install and configure yourself | The account whose credentials you used | Often | No | | Your shared inbox’s own MCP server | Connect by sign-in | The team’s shared mailboxes you can access | Keeping’s: drafts only | Yes | The table reflects Google’s, Anthropic’s and OpenAI’s help pages on November 3, 2026. Several shared inbox and help desk tools now publish MCP servers of their own. The difference from everything above is the last column: they work on the team’s queue, with owners and statuses, instead of a personal mailbox. ## Is there a Gmail MCP server for a shared inbox? Not from Google. Every Gmail MCP option above, official or built in, acts as the one person who signed in. A team inbox like support@ usually lives in one of three places, and none of them gives an assistant the shared view. **A shared Workspace account with delegates.** The assistant can see support@ only if someone signs in to it as support@ itself. Delegates can’t use Gemini in the delegated account, per Google’s [Gmail delegation help](https://support.google.com/mail/answer/138350), and a [Google Workspace shared mailbox](https://www.keeping.com/content/google-workspace-shared-mailboxes/) built this way has no idea who owns which email. **A Google Groups collaborative inbox.** There’s no MCP server for Google Groups. Messages arrive in each member’s own inbox, so an assistant connected to one person sees copies, not the group’s queue. Our guide to the [Google Groups collaborative inbox](https://www.keeping.com/content/google-groups-collaborative-inbox/) covers where it stops. **One person’s connector reading forwarded copies.** If support@ forwards to you, your assistant can read your copy and draft from it. Nobody else sees what it did, and the draft sits in your mailbox, not the team’s. What’s missing in all three is the team layer: who owns each email, its status, internal notes, a warning when two people start the same reply, and response-time reports. That’s the job of a shared inbox, and it’s why teams that [manage a support@ address in Gmail](https://www.keeping.com/content/gmail-shared-mailbox/) move past [Gmail delegation](https://www.keeping.com/content/gmail-delegation/) once more than a couple of people answer. If your team needs assignment and status from the assistant, the next section is the setup that gives it. ## Connect your assistant to the team inbox with Keeping’s MCP server Keeping runs your shared inbox inside Gmail, and its MCP server gives Claude, ChatGPT or Gemini the team’s conversations, not just one person’s mailbox. Each person connects with their own Keeping sign-in, so the assistant reaches only the shared mailboxes that person can already see in Keeping. Once connected, your assistant can: - Search and read the team’s conversations, notes and history - Draft replies on a conversation - Assign conversations, tag them, change status and add internal notes - Run team, ticket and SLA reports Drafts never send. Each draft is saved on the conversation, where a teammate reads it, edits it if needed, and presses send from Gmail or the Keeping app. Keeping’s MCP server comes with [every plan](https://www.keeping.com/pricing/): limited MCP access on Essentials, full on Advanced and HIPAA. ### How to connect Keeping to your assistant - **Claude:** Keeping is listed in Claude’s connectors directory as “by Keeping,” so you add it from Customize, then Connectors, without typing a server URL. - **ChatGPT:** you add Keeping on the ChatGPT website as a custom MCP server under Plugins. It works on every ChatGPT plan, including Free. - **Gemini:** you add Keeping as a custom app in Gemini on the web. Work and school accounts can’t sign in to Gemini custom apps yet, so you sign in to Gemini with a personal Google Account. Google also requires you to be 18 or older, in the United States, using Gemini in English, with Keep Activity turned on. A Workspace user can still connect: when Keeping asks you to sign in during setup, use the Google account you use for Keeping, which can be your work account. - **Antigravity CLI, Gemini CLI and other MCP clients:** add `https://mcp.keeping.com/` as a remote server and sign in when prompted. The step-by-step setup for each assistant is in Keeping’s guide to [connect Keeping to Claude, ChatGPT or Gemini](https://docs.keeping.com/help/mcp-server/connecting-to-keepings-mcp-server). For the Gemini walkthrough, permission levels and five prompts for a support@ morning, see how to [run your Gmail shared inbox from Claude, ChatGPT, or Gemini](https://www.keeping.com/content/gmail-shared-inbox-mcp/). Want your assistant to have the team inbox, not just yours? [Try Keeping free for 14 days](https://app.keeping.com/signup), no card needed, connect support@, and add Keeping to the assistant you already use. ## Is it safe to connect an AI assistant to Gmail? It can be, if you keep the access narrow and a person in the loop. Four things to check before you connect anything: - **Scopes.** Read-only access can’t change anything. Compose access can write drafts. Full Gmail access can send and delete, so give it only to a tool you trust. - **Approvals.** Claude asks before each Gmail action by default, and ChatGPT workspaces keep write actions off until an admin turns them on. Leave those defaults alone for a work account. - **Prompt injection.** Google’s own setup guide warns that incoming email can carry hidden instructions. A support inbox receives mail from strangers all day, so assume some of it will try. - **Drafts versus sends.** For customer email, a server that only drafts is the safer default. A mistake in a draft costs a minute to fix, and a mistake in a sent reply reaches the customer. ## Frequently asked questions about Gmail MCP ### Does Google have an official Gmail MCP server? Yes. Google hosts a remote Gmail MCP server as part of its Google Workspace Developer Preview Program, alongside servers for Drive, Docs, Sheets, Slides, Calendar, Chat, People and Classroom. You join the preview, set up a Google Cloud project and OAuth client, then add the server to Claude, Antigravity or another MCP client. ### Can the Gmail MCP server send email? No. Google’s Gmail MCP server can search and read threads, manage labels and create drafts, but it has no send tool. A draft lands in your Gmail drafts folder and you send it yourself. Claude’s own Gmail connector can send, reply and forward, and asks for your approval first by default. ### Is Google’s Gmail MCP server free? Google’s setup pages don’t list a charge for the Gmail MCP server. You do need membership in the Developer Preview Program and a Google Cloud project, and preview terms apply. The assistant you connect it to has its own plan rules: Google names Claude Pro, Max, Team and Enterprise. ### Does it work with a personal Gmail account? It’s built for Google Workspace accounts. Google’s Developer Preview Program registers a Workspace account and a Cloud project, and its setup pages don’t describe a path for a personal @gmail.com address. If you’re on personal Gmail, the Gmail connection built into Claude, ChatGPT or Gemini is the simpler route. ### Is there a Gmail MCP server for a shared inbox? Not from Google. Its Gmail MCP server and the assistants’ Gmail connections all act as the one person who signed in, so they can’t see who owns a support@ conversation or change its status. A shared inbox tool with its own MCP server, such as Keeping, gives your assistant the team’s queue.