MCP connectorsGmail

Gmail MCP: connect Gmail to Claude and ChatGPT

Ask Claude or ChatGPT what the supplier said about the delivery date, which customer emails from this week still need an answer, or to draft a reply to Anna’s last message. The answer comes from your own inbox, read thread by thread.

With Deployed OS everyone connects their own Google account. The AI reads only that person’s mail, and drafts wait in their Drafts folder. Nothing is ever sent.

2 read actions · 1 write action · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Gmail in Claude and ChatGPT

Sales

Catch up before the call

Every message with the prospect since the first demo, summarised in five lines before you dial. Then a follow-up drafted in the same thread, ready for you to send.
Customer success

Reply with the history in front of you

Find what the customer wrote last time and what you promised. Get a reply drafted as an answer in the thread. You read it, adjust it and press send.
Management

The Monday inbox

Ask what came in since Friday that needs you. Get the threads that matter, two lines each, before the Monday meeting instead of after it.
Operations

Find the email you know exists

The booking confirmation, the delivery date, the address someone sent in March. Ask in plain words and get the thread back, with who said what and when.
Examples

Ask it like this

  • “Summarise my thread with Erik at Nordbygg about the delivery date. What did we agree?”

  • “Which emails from customers this week haven’t I answered yet?”

  • “Find the email where Lisa confirmed the venue for the kick-off and give me the date and address.”

  • “Draft a reply to Anna’s last email: yes to Thursday at 10, and ask her to bring the signed order.”

  • “What has Acme written to us since the start of the month? Five bullets.”

  • “Go through my unread email from the last two days and tell me which three need me today.”

The connector

What the Gmail MCP connector does today

  • Readsgmail_search

    Searches your own Gmail with Gmail’s search operators, such as from:anna or newer_than:7d. Returns sender, recipients, subject, date and a snippet for up to 20 messages.

  • Readsgmail_read_thread

    Reads one of your threads as text, message by message, with sender, recipients, subject and date. Attachments are not read, and very long messages are cut at 20,000 characters.

  • Writesgmail_create_draft

    Creates a plain-text draft in your Drafts folder, new or as a reply in the same thread. Nothing is sent: you open it, check it and press send yourself.

Need it to do more? We extend connectors for the companies that use them.

Security

Who sees what

Reads mail, writes drafts
The connector searches and reads your own mail and creates plain-text drafts. It cannot send, forward, delete or label anything in Gmail, and drafts follow your company’s guardrails for AI use.
Only your own mailbox
Everyone connects their own Google account, so the AI reads that person’s mail and nobody else’s. A colleague’s inbox stays theirs.
You choose who gets it
Admins decide which groups at the company can use the Gmail connector, and which of them may also create drafts. Everyone else never sees it.
Every call logged
Who searched, who drafted, when. Deployed OS shows reads and writes per connector and per person, the log can be exported, and access is revoked centrally the day someone leaves.
Setup

Set up the Gmail connector in three steps

01
An admin creates a project in your company’s Google Cloud, sets up an internal OAuth app and turns on the Gmail API. The same Google app serves Drive, Calendar, Analytics and Ads, and your company owns it.
02
The admin adds the app’s Client ID and Client secret to Deployed OS and chooses which groups get Gmail.
03
Each person connects their own Google work account. From then on they just ask, in Claude, ChatGPT or Copilot.
Compared

Gmail’s own MCP server or Deployed OS?

Google runs its own remote MCP servers for Gmail, Drive and Calendar. A developer turns them on in a Google Cloud project and connects an AI client. For one person, or a developer building an agent, that is a good fit.

Deployed OS is built for the whole company: one connection for Gmail and the rest of your tools, each person’s own login, admins choosing which groups get what, and a log of every call. The same connection works in Claude, ChatGPT and Copilot, next to your company’s skills and guardrails.

Their documentation: Google’s MCP server

Questions

Gmail MCP: common questions

Yes. Google runs remote MCP servers for Gmail, Drive and Calendar that a developer sets up in a Google Cloud project. Deployed OS gives the whole company one connection instead, with each person’s own login, access per group and a log of every call.

No. The connector searches and reads your mail and saves drafts in your Drafts folder. It never sends, forwards, deletes or labels anything: you open the draft and press send yourself. If you want it to do more, for example label threads, we can extend it for you.

Claude’s own Gmail connector links one person’s Gmail to Claude. Deployed OS is your company’s own Gmail MCP server: the same connection works in Claude, ChatGPT and Copilot, runs on your company’s Google app, admins choose which groups get it, and every call is logged.

No. The Google app is internal to your company’s Google Workspace, so only work accounts in it can connect. That keeps the connector to company mail.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. On-premises is possible too. Mail is fetched from Gmail when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.

Poyan Karimi
You’ll hear from Poyan Karimi
Co-founder · Deployed AI