Gmail

@Gmail fetch all unread emails from the last 3 days that mention 'budget approval' and summarize the key action items by sender

Found 7 unread messages matching your criteria. From Sarah Chen (Finance): needs Q4 budget reallocation signed by Friday, $45K shift from marketing to engineering. From Mike Torres (Ops): requesting approval for $12K server upgrade, waiting since Monday. From Jennifer Park (Product): asking to reallocate $8K from unused travel budget to user research. The remaining 4 messages are FYIs or automated notifications with no action required. All three requests include attached spreadsheets breaking down the line items.

This example shows fetch + AI synthesis working together. The MCP retrieves message metadata and bodies; the AI extracts action items. Requires Gmail read scope. Note that 'last 3 days' filtering uses Gmail's query syntax under the hood, which may behave unexpectedly with timezone boundaries or complex boolean logic.

@Gmail create a draft reply to the most recent email from james@vendor.com thanking him for the proposal and asking for a revised timeline with Q2 milestones

Draft created and saved to your Gmail drafts folder. The reply is threaded under James's original message (subject: 'Proposal for Infrastructure Refresh'). Draft body: 'Hi James, Thanks for sending over the proposal—the scope looks solid. Before we move forward, could you revise the timeline to include specific Q2 milestones? We need to align this with our board reporting calendar. Best, [Your Name]'. You can edit or send this draft from Gmail.

Demonstrates draft creation with threading context. The MCP finds the most recent message from the sender, then creates a reply draft in the same thread. This is a write operation but non-destructive—you review before sending. Requires Gmail compose scope. If multiple recent emails exist from that sender, the MCP picks the newest by date.

@Gmail create a label called 'Q1-2025-Contracts' and move all emails from legal@company.com in January to that label, then tell me how many were moved

Label 'Q1-2025-Contracts' created successfully. Searched for messages from legal@company.com sent between January 1-31, 2025, and applied the new label to 14 messages. These emails remain in your inbox (labels in Gmail don't remove messages from other views—they're tags, not folders). The labeled messages include 9 contract PDFs, 3 signature request threads, and 2 follow-up reminders.

Shows label creation plus batch message modification. This is a write operation that changes your mailbox organization. Gmail labels are additive—messages keep their existing labels and locations. Requires Gmail modify scope. If you later delete the label, the messages stay in your inbox. Be cautious with broad date ranges; this could label hundreds of messages if the sender is prolific.

When Gmail MCP beats a ticketing system for small teams

A 3-person support team handling 40-60 inbound emails daily can use the Gmail MCP to triage, label, and draft responses without paying for Zendesk. The fetch-and-filter tools let you pull unread messages by sender domain or subject pattern, then auto-label them by urgency or product area. The draft tool supports threading, so follow-ups stay grouped. This works until you hit about 100 emails per day or need SLA tracking—at that volume, you want a real ticketing system with assignment rules. Below that threshold, the Gmail MCP keeps your workflow in one place and costs nothing beyond OAuth setup. If your team already lives in Gmail and you're pre-revenue, this is the right call for the next six months.

Why the Gmail MCP isn't built for bulk sends

A 2-person marketing team drafting a weekly newsletter to 300 subscribers should not use the Gmail MCP for the actual send. Gmail's API rate limits and deliverability rules make it a poor fit for bulk email—you'll hit sending caps fast and risk your domain reputation. The MCP is useful for the prep work: fetching replies from last week's send, pulling contact lists via the Get Contacts tool, and creating labeled drafts for review. Once the draft is approved, hand off to Mailchimp or SendGrid for the actual blast. The boundary is simple: if you're sending to more than 50 recipients at once, the Gmail MCP is a research and drafting tool, not your delivery layer.

When Gmail MCP handles outbound without a CRM

A solo founder or 2-person sales team doing 10-15 outbound touches per week can use the Gmail MCP to automate follow-ups and thread tracking without buying HubSpot. The Fetch Message by Thread ID tool lets you check if a prospect replied, then the Create Draft tool queues a follow-up with the right context. The label tools let you tag threads by deal stage or next action date. This breaks down around 50 active threads—beyond that, you lose visibility and need a real CRM's pipeline view. But if you're pre-Series A and your deal count is low, the Gmail MCP keeps your outbound workflow in the inbox you already check. Pair it with a calendar MCP for meeting scheduling and you're covered through first revenue.