CommsConnector
Gmail
Search and read Gmail, draft replies, send, archive or trash mail from Claude or ChatGPT through Tulina's MCP server, on a Google sign-in limited to Gmail.
Official site: mail.google.com
What it can do
2 send
- 01Send
Search messages and read them, with attachments
- 02Send
Draft replies, send a draft, archive or trash mail
Gmail through Tulina searches your mailbox, reads messages and attachments, writes drafts and sends mail from Claude or ChatGPT. Drafting and sending are separate tools. A draft never leaves the mailbox, and a send is a distinct call that your client asks you to confirm.
Is there an MCP server for Gmail?
Yes. Google hosts one at gmailmcp.googleapis.com. Google's documentation labels it a Developer Preview, available through the Google Workspace Developer Preview Program, and its page was last updated on 21 July 2026. You create a Google Cloud project, enable the Gmail API and the Gmail MCP API, set up an OAuth consent screen and an OAuth client, then add the server to Claude as a custom connector with that client ID and secret. Tulina's connector is the other route: one authorization click, held in the same MCP link as the rest of your tools.
How do you set up the Gmail MCP for Claude and ChatGPT?
Through Tulina's MCP server, in three steps:
- In Tulina, open the Gmail connector and click Authorize Gmail. Google asks you to approve Gmail only, with the
gmail.modifyscope, on the account you choose. - Connect more Google accounts if you want them. Each one is named by its address, and the agent picks one per call or asks which when no default is set.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.
No Google Cloud project, consent screen or OAuth client is needed on your side.
Tulina vs Google's official Gmail MCP server
Google's server is the first-party route. Tulina's connector covers the mail actions Google's tool list leaves out.
| Google's Gmail MCP server | Tulina | |
|---|---|---|
| Endpoint | gmailmcp.googleapis.com/mcp/v1, hosted by Google | mcp.tulina.ai/mcp, one link for every connected tool |
| Setup | Your Google Cloud project, consent screen and OAuth client | Authorize Gmail from the connector card |
| Scopes | gmail.readonly and gmail.compose | gmail.modify |
| Search and read | Search threads, get a thread, get a message | Search messages, get a message |
| Attachments | Not in the tool list | Read an attachment as text, CSV per sheet for .xlsx, or a signed link |
| Drafts | Create and list drafts | Write a draft or a threaded reply, list drafts |
| Send | Not in the tool list | Send a draft, or a full message |
| Archive and trash | Not in the tool list | Archive, move to trash |
| Labels | List, create, apply and remove | Not available |
| Several accounts | Not covered on Google's page | Several Google accounts and shared mailboxes, chosen per call |
If the work is about labels, or you want a read-and-draft server with no send tool at all, Google's own server is the better choice. Tulina fits when the mail step belongs to a longer piece of work that also touches your CRM, your calls or your calendar.
What you can ask it
"Find this week's unread emails from customers and tell me which need a reply." The agent searches with Gmail query syntax such as is:unread newer_than:7d, reads the messages that matter and returns a short list with the reason for each.
"Draft a reply to Marie's last message confirming Thursday." The agent writes a threaded draft with the subject and thread preserved, appends your Gmail signature and stops. You read it in Gmail, then say send, and the agent sends that draft as it stands.
"Read the devis spreadsheet attached to Paul's email and archive the thread." The agent reads the attachment, which comes back as CSV per sheet and truncated if the sheet is long, summarises it, and archives the message once you agree.
Gmail pairs with HubSpot when a reply should be logged on the deal, and with Calendar when a thread ends in a meeting. These processes use it: Follow through on sales calls, Re-engage quiet accounts and Keep your knowledge base current.
What the Gmail connector can't do
- It has no label tools. It cannot list, create, apply or remove labels. Archive removes the Inbox label and nothing else.
- It does not delete for good. Trash moves messages to the trash, and Gmail deletes them after 30 days. Trash goes one message per call, so a long list can end partway and the agent names what was not done.
- The scope is
gmail.modify, which is broader than read and compose. The connector sends, archives and trashes, so Google's consent screen asks for that access. - A draft is sent exactly as written. Edit it in Gmail first if you want changes. A fresh draft can take a moment to appear in an open Gmail tab, so reload or search
in:drafts. - The agent's replies carry your Gmail signature by default. Write no sign-off of your own, or ask for no signature.
- Text attachments come back inline up to 256 KB and other files as a signed link, and a scanned or protected PDF has no extractable text. Spreadsheets return 200 rows a sheet by default and 5,000 at most.
- No tool walks through several accounts at once. A total across mailboxes is one call per account.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Gmail once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Gmail at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Gmail returns something usable instead of something generic.
Processes that run on Gmail
Chase failed direct debits
Each failed direct debit is matched to its invoice, skipped if paid, retrying or already chased, and given a reminder draft that fits why it failed.
7 steps →Draft the monthly investor update
Revenue, pipeline, the plan's own targets, and last month's commitments are pulled together into a draft with the numbers already in it.
5 steps →Draft the quarterly LP letter
Portfolio metrics gathered from founder updates and dashboards, drafted into your quarterly letter, with every figure carrying the date it was reported.
5 steps →Expand accounts from usage
Each morning, accounts near a plan limit or on a feature their plan lacks get an offer priced on your packaging rules, an expansion deal and a drafted proposal.
7 steps →Find local points of sale
Every target city is searched three different ways for shops that fit your positioning, each one ranked on fit and reviews before the first email goes out.
5 steps →Follow champions who change jobs
Each week, champions at won accounts are checked for a new employer, the new company is scored on your ICP, and a warm deal opens with a note for the right rep.
7 steps →Follow through on sales calls
After every sales call, the follow-up email is drafted from what was said, the deal gets a dated next step, product asks are filed and any risk is flagged.
7 steps →Keep your knowledge base current
An AI knowledge base kept current each morning: yesterday's activity in your tools is read, stale pages are rewritten in place, and a missed day sends an alert.
7 steps →Re-engage quiet accounts
Quiet paying accounts get one relevant note each, grounded in what they said last, with the outreach date stamped back so nobody's emailed twice.
7 steps →Revive deals that went cold
Deals lost more than 90 days ago come back with fresh signals, contacts checked for job moves, and the features they asked for that have since shipped.
6 steps →Turn signups into pipeline
PQL scoring for every trial signup: enriched, scored on your ICP, the first session read, a play chosen by your rules and a deal opened for the right rep.
7 steps →
