Connect Google Workspace to Claude,
and ChatGPT, Cursor, any MCP client
Give your AI agent the company mailboxes that live in Google Workspace on your own domain: yours, sales@, support@ and the rest. It reads, searches, sends, replies, schedules and organizes mail over IMAP with an app password, and the same mailboxes work in every MCP client, not just one.
A Google Workspace mailbox on your own domain is a Gmail mailbox underneath, so it connects to mcpemails the way Gmail does: with a Google app password over IMAP and SMTP at imap.gmail.com and smtp.gmail.com. mcpemails is a hosted MCP server, so once the mailbox is connected Claude, ChatGPT, Cursor or any MCP client can read, search, send and organize its mail. Your Workspace administrator's settings decide whether an app password is available and whether IMAP is allowed.
How Google Workspace connects: an app password over IMAP
Type your address in the IMAP form and mcpemails reads your domain's MX records: a domain whose mail goes to Google (aspmx.l.google.com or smtp.google.com) is recognised as Google Workspace, and the form fills in imap.gmail.com on 993 and smtp.gmail.com on 465 and tells you an app password is required. Choosing the Gmail card does the same. Google turned off password sign-in for Workspace apps in 2025, with the exception of app passwords, so the account password will never work here. Signing in with Google is offered as an alternative.
Personal @gmail.com address? Connect Gmail
The exact Google Workspace IMAP and SMTP settings
Copy these into the connect form. mcpemails prefills them where it can, and retries the other standard transport if the first does not answer.
| Protocol | Server | Port | Security |
|---|---|---|---|
| IMAP (incoming) | imap.gmail.com | 993 | TLS (implicit) |
| SMTP (outgoing) | smtp.gmail.com | 465 | TLS (implicit) |
Verified 2026-08-31: imap.gmail.com answered a TLS connection and identified itself as an IMAP server under that name. It advertises OAUTHBEARER, PLAIN, PLAIN-CLIENTTOKEN, XOAUTH2 authentication.
Sign in with: The full address on your own domain, for example info@yourcompany.com. The app password replaces the account password, which will not work.
A Google Workspace inbox your agent can actually use
Seventeen action-based MCP tools: send, reply, forward, schedule, and organize. Your agent finishes the job inside Google Workspace.
- 01Read
Read & search mail
List, read and search across folders to find that invoice, summarize a thread, or pull the latest from a sender.
- 02Send
Send, reply & forward
Compose and send real messages, reply in-thread, and forward, directly from your mailbox, not as a draft you finish by hand.
- 03Schedule
Schedule for later
Queue a message to go out at the right time, so your agent can draft now and send on schedule.
- 04Organize
Move, copy, flag, archive, delete
Keep the inbox tidy: file mail into folders, flag what matters, archive the rest, or delete on request.
Connect Google Workspace in four steps
From sign-up to first AI email in a couple of minutes.
Create a free account
Sign up for mcpemails, no card required. The free plan connects one inbox, forever.
Create a Google app password
Signed in as the mailbox you want to connect, switch on 2-Step Verification if it is not on, then create an app password at myaccount.google.com/apppasswords. If the option is missing, your administrator's settings are the likely reason (see below).
Paste it into mcpemails
Choose IMAP / SMTP or Gmail, type the full address on your domain, and paste the 16-character app password. The hosts are filled in from your domain.
Paste the MCP URL into your AI
Drop https://mcpemails.com/api/mcp into Claude, ChatGPT or Cursor, authorize, and your agent has the mailbox. Repeat the app password step for each company mailbox you want it to reach.
Comparing providers first? See the email provider compatibility matrix
Every Google Workspace mailbox your company runs, on one agent
If your company runs more than one address on Google Workspace, such as info@, sales@ and invoices@, connect each one to the same mcpemails workspace. Your AI client then reaches all of them through the one MCP URL, in Claude, ChatGPT, Cursor or any other MCP client. Every tool call names the mailbox it acts on, each mailbox keeps its own sender name and signature, and a reply goes out through the mailbox it belongs to.
Free connects one mailbox, Personal three, and Pro every mailbox you run, on one login.
What actually goes wrong with Google Workspace
The app password option can be missing on a Workspace account
Google offers app passwords only on accounts with 2-Step Verification on, and its own help page lists three reasons the option may not appear even then: 2-Step Verification set up only with security keys, Advanced Protection, or being signed in to a work, school or other organization account whose settings do not allow it. The last one is your administrator's decision and nothing inside the mailbox changes it. Ask the admin, or connect with Google sign-in instead if your organisation allows third-party apps.
IMAP is switched on by the administrator, not by you
On Google Workspace, users cannot turn IMAP on or off in their own Gmail settings. An administrator does it in the Google Admin console under Apps, Google Workspace, Gmail, End User Access, in the POP and IMAP access section, for everyone or per organizational unit. Two settings there decide whether an app password works: IMAP must be enabled for your unit, and the admin must have chosen Allow any mail client. If they restricted IMAP to named OAuth mail clients only, an app password login is refused however correct it is.
An alias is not a mailbox, and neither is a group
Workspace lets an admin add up to 30 aliases to one user, and mail sent to an alias lands in that user's own inbox. An alias has no sign-in of its own, so you connect the user it belongs to and the alias's mail is already there. A Google Group address (a mailing list or a collaborative inbox) is not an account you can sign in to either, so it has no app password to connect: connect a member's mailbox. Only real user mailboxes connect, each with its own app password, and each one counts as one connected inbox.
Replying from an alias needs the Google sign-in connection
With an app password, a mailbox sends from its own address. Sending from a different address, such as an alias set up as a Gmail Send mail as address, is supported only on a mailbox connected by signing in with Google, where the verified Send As addresses are listed for your agent. On any other connection a From address that is not the mailbox's own is refused, not silently rewritten.
Known limits with Google Workspace
- mcpemails reaches mail only: an app password is used for IMAP and SMTP alone. Drive, Calendar, Chat and Docs are not reached.
- A Google Workspace administrator can close both routes: app passwords may be unavailable to your account, IMAP can be off or limited to named OAuth clients, and third-party access can be blocked for the Google sign-in option. Only an administrator can change those settings.
- Gmail stores labels, not folders, so a move adds one label and removes another, and delete moves a message to Gmail's Trash.
Google Workspace and AI: common questions
Does Claude work with Google Workspace email?
Yes, once an MCP server such as mcpemails connects the mailbox. A Workspace mailbox on your own domain connects with a Google app password over IMAP, exactly like a gmail.com address, and Claude can then read, search, send, reply and organize its mail. The same connection works in ChatGPT, Cursor and any other MCP client.
What are the Google Workspace IMAP and SMTP settings?
IMAP is imap.gmail.com on port 993 with SSL/TLS, and SMTP is smtp.gmail.com on port 465 with SSL/TLS. The username is your full address on your own domain and the password is a Google app password. mcpemails fills these in when your domain's MX records point at Google.
Why can I not create an app password on my Workspace account?
Google lists three reasons: 2-Step Verification is set up only with security keys, the account has Advanced Protection, or it is a work, school or organization account whose settings do not allow app passwords. The first two you can change yourself; the third is an administrator decision.
Why is my app password rejected when it is correct?
Most often because IMAP is not allowed for your account. On Workspace only the administrator can turn IMAP on, per organizational unit, and they can restrict it to named OAuth mail clients, which refuses app password logins. Ask them to enable IMAP with Allow any mail client for your unit.
Can I connect info@, sales@ and support@ from the same Workspace?
Yes, when each one is a real user mailbox: connect each with its own app password and your agent reaches all of them through one MCP URL. An alias or a Google Group address is not a mailbox of its own, so connect the user mailbox its mail is delivered to.
Is my Google Workspace mail stored on your servers?
No. Messages are fetched live from Google for each request and handed to your AI client. The app password, or the OAuth token if you sign in with Google, is encrypted at rest and message bodies are not retained. Revoking the app password in your Google Account, or deleting the inbox in mcpemails, ends the connection.
Can I connect several Google Workspace mailboxes to the same AI agent?
Yes. Connect each Google Workspace address to one mcpemails workspace and your AI client reaches all of them through the same MCP URL. Every tool call names the mailbox it acts on, so a reply to a message in sales@ goes out from sales@. Free connects one mailbox, Personal three, and Pro every mailbox you run.
Give your AI your company's Google Workspace mailboxes
Connect the first one in minutes. One inbox free forever, no card required.