Gmail
Give your agent Gmail send, read, and search so support replies, validation outreach, and inbox triage happen inside the coding session.
Overview
Gmail MCP is a Build-phase MCP server that lets AI agents send, read, and search Gmail using Google OAuth credentials.
What is this MCP server?
- Gmail MCP v0.1.0 by Strider Labs over stdio transport
- Send, read, and search mail from the agent without custom IMAP scripts
- Google OAuth 2.0 via GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_REFRESH_TOKEN
- npm package @striderlabs/mcp-gmail with GitHub source
- Published server version 0.1.0
- 3 required Google OAuth environment variables
- npm identifier @striderlabs/mcp-gmail with stdio transport
What problem does it solve?
Founders lose flow when every customer email forces a browser tab and bespoke Gmail API code instead of agent-native inbox tools.
Who is it for?
Solo builders automating founder inbox work, waitlist replies, and project email from Claude Code, Cursor, or Codex.
Skip if: Organizations that require workspace-wide admin consent, DLP, or bulk marketing sends without personal OAuth tokens on a dev machine.
What do I get? / Deliverables
After OAuth setup, your agent can query and act on Gmail from MCP tool calls aligned with your shipping and support routines.
- Agent-accessible Gmail send, read, and search tools
- Reusable inbox integration without per-project Gmail SDK boilerplate
- stdio MCP registration documented for your agent config
Recommended MCP Servers
Journey fit
Email MCP belongs in build integrations because it is how solo builders wire production communication into agents alongside code and deploy tooling. Gmail over OAuth refresh token is a standard third-party API integration pattern for MCP, not a standalone shipping or growth playbook.
How it compares
OAuth-backed email MCP integration, not an email copywriting skill or a transactional ESP product.
Common Questions / FAQ
Who is Gmail MCP for?
It is for developers and solo founders who want their coding agent to read and send Gmail for product and support tasks.
When should I use Gmail MCP?
Use it while building or operating a product when inbox search, replies, or outbound mail should run next to your repo and deploy tools.
How do I add Gmail MCP to my agent?
Install @striderlabs/mcp-gmail, create Google OAuth credentials in Cloud Console, obtain a refresh token for your mailbox, and register the stdio server with those three env vars.