Google Gmail
Draft, send, triage, and label Gmail from the agent for onboarding replies, waitlist nurture, and support threads while you scale users.
Overview
com.mcparmory/google-gmail is a Grow-phase MCP server that sends, reads, and organizes Gmail with labels, drafts, and filters from your agent.
What is this MCP server?
- Send and read Gmail messages through MCP stdio (PyPI uvx or Docker OCI).
- Organize with labels, drafts, and filters to keep founder inbox workflows sane.
- Version 1.0.4 of com.mcparmory/google-gmail from the mcparmory registry.
- Supports agent-assisted reply drafts and thread summarization prep (tooling via Gmail API).
- Communication-focused MCP, not a full marketing automation platform.
- Server version 1.0.4
- 2 install artifacts: PyPI mcparmory-google-gmail and OCI ghcr.io/mcparmory/google-gmail:1.0.4
- stdio transport per server.schema.json
Community signal: 25 GitHub stars.
What problem does it solve?
Indie founders drown in onboarding and support mail because switching to Gmail breaks the flow of agent-assisted product and growth work.
Who is it for?
Solo builders who run support and lifecycle email from a personal or workspace Gmail and want agent help on threads and organization.
Skip if: Teams needing bulk transactional email infrastructure, strict compliance archive, or non-Google mail providers only.
What do I get? / Deliverables
With this MCP server registered, your agent can draft, send, and sort Gmail so lifecycle email stays inside the same build-and-grow session.
- Agent-drafted and sent Gmail messages for defined threads
- Applied labels and filter updates for support or nurture streams
- Organized inbox state your agent can reference in later tasks
Recommended MCP Servers
Journey fit
Gmail MCP sits in Grow because founders use it for ongoing user communication after launch rather than for initial product scaffolding. Lifecycle covers repeatable email touchpoints—onboarding, retention, and lightweight support—that agents can assist with via inbox tools.
How it compares
Gmail inbox MCP connector, not a drip-campaign skill or ESP integration pack.
Common Questions / FAQ
Who is com.mcparmory/google-gmail for?
It is for founders and small teams using Gmail who want Claude Code or Cursor to read, send, and organize mail via MCP.
When should I use com.mcparmory/google-gmail?
Use it in Grow when handling user replies, drafting onboarding messages, or cleaning up labels and filters alongside product iteration.
How do I add com.mcparmory/google-gmail to my agent?
Add the stdio server using uvx mcparmory-google-gmail or Docker ghcr.io/mcparmory/google-gmail:1.0.4 and authorize Gmail OAuth scopes from the registry guide.