Gmail
Let your agent read, send, archive, and manage Gmail so support replies, founder outreach, and lifecycle email stay inside your coding workflow.
Overview
Gmail MCP is a MCP server for the Grow phase that lets agents read, send, archive, and manage Gmail through OAuth-backed tools.
What is this MCP server?
- Read, send, archive, and manage Gmail from MCP tools per registry description
- Google OAuth via GOOGLE_ACCESS_TOKEN (stdio) or client ID/secret in HTTP mode
- Version 2.3.1 with stdio and streamable-http packaging options
- Supports founder support, waitlist replies, and scripted outreach from the agent
- HTTP mode uses MCP_TRANSPORT=http plus Google OAuth app credentials
- Server version 2.3.1
- Required secret: GOOGLE_ACCESS_TOKEN (stdio)
- Two transports: stdio and streamable-http with OAuth env vars
Community signal: 7 GitHub stars.
What problem does it solve?
Founder inboxes pile up with user email while you are still coding, and copying context into the agent by hand wastes time and drops threads.
Who is it for?
Solo SaaS founders who handle support and lifecycle email in Gmail and use MCP agents daily.
Skip if: Teams needing bulk cold email, CRM replacement, or sending without Google OAuth and scope review.
What do I get? / Deliverables
Your agent can work inside Gmail via MCP so triage, drafts, and archiving happen from the same session where you ship fixes.
- Agent-driven Gmail read, send, archive, and management actions
- Faster inbox triage tied to your shipping workflow
Recommended MCP Servers
Journey fit
Gmail MCP maps to Grow because solo builders use it to run customer communication, follow-ups, and inbox hygiene while the product is live—not while wiring core product code. Lifecycle covers ongoing user and lead email touchpoints that agents can draft, triage, or archive without opening a separate admin tool.
How it compares
Gmail MCP integration for agents, not a newsletter skill or transactional email API wrapper alone.
Common Questions / FAQ
Who is Gmail MCP for?
Builders who run product support and founder email in Gmail and want MCP agents to read, send, and organize messages responsibly.
When should I use Gmail MCP?
Use it during Grow when you triage user mail, draft lifecycle replies, or archive resolved threads while building in parallel.
How do I add Gmail MCP to my agent?
Install gmail-mcp via npx with stdio and provide GOOGLE_ACCESS_TOKEN with Gmail scopes, or run HTTP mode with MCP_TRANSPORT=http, GOOGLE_CLIENT_ID, and GOOGLE_CLIENT_SECRET per server.json.