Connect Gmail to Claude via MCP — attachments, scheduling, every AI

The native Claude Gmail connector now sends, but from one Google account at a time and without attachments. MailMCP gives your AI full Gmail access: sending with files, reply chains, scheduling, search — everything via MCP.

Connect Gmail to AI Setup guide

The problem with the native Claude Gmail connector

Claude.ai offers a built-in Gmail connector. Since August 2026 it can send, each email approved by default. But it cannot attach the quote you mention, schedule a follow-up, or work outside Claude. For one email, that is fine. For 20 emails a day with files, it defeats the purpose of AI assistance.

Claude native Gmail — limitations

No attachments sent: it only sees their metadata
One Google account at a time
No scheduled sending
Cannot move, flag or organize emails
Only works with Claude — not ChatGPT, Cursor, etc.

MailMCP + Gmail — full access

Sending with attachments: by link, uploaded in chunks, or inline images
Reply in existing threads with full context
Schedule emails for later — exclusive MailMCP feature
26 tools: search, flag, move, create folders, and more
Works with Claude, ChatGPT, Cursor, n8n and more

Why MCP is better than native connectors for email

The Model Context Protocol (MCP) is an open standard that lets AI tools interact with external services. Unlike native connectors locked to a single AI vendor, MCP gives you freedom, power, and consistency across all your tools.

Universal compatibility

One MailMCP configuration works with Claude, ChatGPT, Cursor, VS Code, Windsurf, n8n, and any MCP-compatible AI. Native connectors only work with one specific AI tool.

Full email capabilities

MailMCP exposes 26 MCP tools, 16 of them for email: read, send with attachments, reply, search, schedule, flag, move, delete, create folders. Native connectors read, draft and send with your approval, but without files. MailMCP gives your AI the power of a complete email client.

Scheduled sending

MailMCP exclusive: schedule emails to be sent at a specific date and time. Your AI can prepare a batch of follow-up emails and have them sent tomorrow at 9 AM. No native connector offers this.

Gmail IMAP/SMTP configuration for MailMCP

MailMCP auto-detects Gmail settings from your email address. Here are the details for reference.

IN IMAP — Incoming mail

Server: imap.gmail.com
Port: 993
Security: SSL/TLS
Username: your @gmail.com address

OUT SMTP — Outgoing mail

Server: smtp.gmail.com
Port: 465
Security: SSL/TLS
Username: your @gmail.com address

Important: Gmail App Password required

If you have 2-Step Verification enabled on your Google account (recommended), you need a Gmail App Password for IMAP access. Go to Google Account > Security > App passwords, create a new password for "Mail", and use the 16-character code in MailMCP. Without this, Gmail will reject the connection.

What you can do with Gmail + MCP that you cannot with native connectors

Real examples of what becomes possible when your AI has full access to your Gmail via MailMCP.

Batch reply to client emails

Ask Claude: "Read all unread emails from clients this week and draft a personalized reply to each one." With native Gmail, each reply waits for your approval by default and leaves without its attachments. With MailMCP, Claude sends them directly with their files — or schedules them for 9 AM tomorrow for your review.

Automated follow-ups

Ask Claude: "Check if John replied to my proposal from last Tuesday. If not, send a polite follow-up with the proposal attached." This requires reading, searching, and sending with a file — the native Gmail connector cannot attach it. With MailMCP, you can even schedule the follow-up for Monday morning.

Inbox organization at scale

Ask Claude: "Move all newsletters to the Newsletters folder, flag all emails from @important-client.com, and mark all social media notifications as read." MailMCP gives your AI the tools to reorganize your entire Gmail inbox in seconds — move, flag, mark, create folders.

Frequently asked questions

Can Claude actually send emails from Gmail, not just create drafts?

Yes. Since August 2026 the native Claude Gmail connector can send too, with your approval by default and from one Google account at a time, but without attachments: it only sees their metadata. With MailMCP, Claude sends directly from your Gmail address with attachments, replies to threads, schedules sending, and works from any MCP-compatible AI.

What is the difference between Claude native Gmail and MailMCP?

Claude native Gmail connector uses the Gmail API: it reads, searches, drafts and, since August 2026, sends with your approval, but it cannot attach a file or schedule a message. MailMCP connects via IMAP/SMTP and the MCP protocol, giving your AI full capabilities: send with attachments, reply, search, schedule, flag, move, create folders — 26 tools in total. MailMCP also works with any MCP-compatible AI, not just Claude.

Do I need a Gmail App Password for MailMCP?

Yes, if you have 2-Step Verification enabled on your Google account (recommended). Generate an App Password from your Google Account > Security > App passwords. Use this 16-character password in MailMCP instead of your regular Gmail password. This is a standard Google security requirement for all IMAP connections.

Can I use MailMCP with Gmail and also ChatGPT or Cursor?

Yes. MailMCP uses the open MCP protocol, so your Gmail mailbox connected via MailMCP is accessible from Claude, ChatGPT, Cursor, VS Code, n8n, and any other MCP-compatible tool. You configure it once and use it from any AI. No vendor lock-in.

Send with attachments. Schedule. From any AI.

Free account, 3-minute setup. Give your AI full access to your Gmail — sending with attachments, scheduling, real actions, from any AI.

Start for free See pricing