How to Connect Claude to Gmail (and When to Give It Its Own Inbox Instead)

Claude can read your Gmail in about two minutes. The official connector is real, it's convenient, and for searching your own mail it's often the right tool. The trouble starts when the same connection becomes the mailbox an agent works from unattended. This guide walks through the setup, the permission settings that matter, and the point where you should stop lending Claude your inbox and give it one of its own.

Two ways people connect Claude to Gmail

When people search for how to connect Claude to Gmail, they usually mean one of two things:

• The Gmail connector in Claude. Anthropic lists Gmail in Claude's connector directory. You sign in with Google once, then turn it on per conversation.
• A Gmail MCP server you wire up yourself. Common in Claude Code and Claude Desktop setups, usually backed by a personal Google OAuth app. We covered the risks of that path in Should You Connect Claude Code to Gmail?

This post focuses on the first one, because it's what most Claude users actually see, and because the safety decisions are the same either way.

How to connect Claude to Gmail with the official connector

1. Check your plan. On Claude Team and Enterprise, an Owner or Primary Owner has to enable the Google Workspace connectors for the organization before Gmail shows up for members.
2. Open connectors. In claude.ai or the Claude app, go to Customize > Connectors, find Gmail, and select Connect.
3. Sign in to Google. Pick the Google account and grant the requested permissions. Google's consent screen mentions sending email; that's expected, because the connector can draft and send when you allow it.
4. If Workspace blocks you. An "Access blocked" message means your Google Workspace admin has to mark Claude as a trusted app under API controls before anyone in the domain can connect.
5. Turn it on in a chat. Select + in the message box, open Connectors, and toggle Gmail on. Then ask something only your mail can answer, like "What did the vendor say about the renewal date?" Claude cites the messages it used.

Set the permissions before your first real question

The connector splits Gmail's tools into read-only tools and write or delete tools, and each one can be set to Always allow, Needs approval, or Blocked. Read tools (search, read a thread, list labels) start on Always allow. Write tools (send, reply, forward, trash, mark as spam, create filters) start on Needs approval. On Team and Enterprise, owners decide whether members can loosen that.

A sensible baseline for a personal account:

• Keep send, reply, and forward on Needs approval. Never switch them to Always allow because the prompts feel slow.
• Block filter creation and trash unless you have a specific job for them. A forwarding filter is the quietest way to leak mail.
• Turn the connector on per conversation rather than leaving it on everywhere.

When the Gmail connector is the right call

Use your Gmail connection when you're in the chat and the mail is yours: summarizing a long thread, finding the message you half remember, drafting a reply you'll read before it goes out. You're the one asking, you see every answer, and approvals happen while you're watching. That's the job the connector was built for.

When Claude should get its own inbox instead

The picture changes once Claude acts as an agent rather than an assistant. Watch for these signs:

• It needs to sign up for tools and receive verification codes or password resets.
• It sends outreach, follow-ups, or support replies under a name that isn't yours.
• It runs on a schedule or a trigger while nobody is there to approve each step.
• Teammates or other agents need to work from the same mail.

In each case, the Gmail connection puts years of personal mail, your Google identity, and your sender reputation behind an automated loop. A dedicated agent inbox gives the agent an address of its own, so a mistake, a prompt injection, or a spam complaint stays contained there.

Set up Claude with a Mermail agent inbox

Mermail runs a hosted MCP email server that Claude can add as a custom connector with OAuth. The setup mirrors the Gmail one, minus your personal account:

1. Create a mailbox. Sign up at console.mermail.app and create an inbox for the agent. The Free plan includes one inbox and 1,000 emails a month.
2. Add Mermail as a custom connector. In Customize > Connectors, add a custom connector with one of the URLs below, then complete the Mermail sign-in and pick your workspace. Custom connectors depend on your Claude plan and workspace settings.
3. Start with the receive-only profile. The agent-inbox profile exposes 12 tools: mailbox discovery, one mailbox create, and scan-gated, sanitized email reads. It has no send, reply, forward, draft, or delete tools, which makes it a good fit for signups and verification codes.
4. Move to the full catalog only for sending. When the agent has an approved send workflow, connect the default URL. Destructive tools there require a short-lived confirmation token, and Claude's own approval settings still apply.
5. Test with a new chat. Send a message to the agent's address from another account and ask Claude to list the newest email. If Claude says it's still finding tools, let it finish once, then make Mermail available for that conversation.

Receive-first (recommended to start):
https://console.mermail.app/mcp?profile=agent-inbox

Full catalog (send, reply, drafts, schedule):
https://console.mermail.app/mcp

Need some Gmail in the loop? Forward it, don't share it

Sometimes the agent genuinely needs mail that lands in Gmail, like support requests or invoices. Instead of connecting the whole account, forward just that slice. In Gmail, add the Mermail address as a forwarding address and approve the verification message, keep account-wide forwarding disabled, then create a filter with a positive rule such as to:support@yourdomain.com and choose Forward it. Send one matching and one non-matching message to confirm only the right mail arrives. If you later reply to a forwarded thread yourself in Gmail, Mermail treats that thread as human-managed and stops AI processing on it.

Quick checklist

• Asking questions about your own mail? Gmail connector, with writes on Needs approval.
• Signups, codes, or anything unattended? A dedicated agent inbox on the receive-first profile.
• Agent needs a few Gmail threads? A selective forwarding filter, not a full connection.
• Sending on its own? Full catalog on the agent's own address, with approvals you actually read.

FAQ

Can Claude send emails from Gmail?

Anthropic's help center says the Gmail connector can draft, send, reply, and forward, and that Claude asks for your approval before each of those by default. What you see can vary by plan and connector version, so check the tool list under Customize > Connectors.

Is it safe to connect Claude to Gmail?

For interactive use with approvals on, it's a reasonable trade. Anthropic says it doesn't train on connector data and that retrieved mail is deleted with the chat. The risk grows when Claude runs unattended or reads mail written to manipulate it, which is when a separate inbox makes more sense.

Does this work in Claude Code?

Claude Code talks to email through MCP servers you add yourself. The same advice holds: give it an agent inbox over MCP rather than an OAuth app on your personal Gmail. Our Claude Code guide has the details.

Can I use both the Gmail connector and an agent inbox?

Yes. Many people keep Gmail on for reading their own mail and give the agent a Mermail address for everything it does on its own. Just turn on only the connector a given conversation needs.

Connecting Claude to Gmail is easy. Deciding which mailbox an agent should live in is the part worth five minutes of thought. Keep your inbox for you, and give the agent one it can't hurt you with.