Gmail
Let your coding agent read, search, and send Gmail from Claude Code or Cursor without leaving the editor.
Overview
com.pulsemcp/gmail is a MCP server for the Build phase that connects coding agents to Gmail using OAuth2 or Workspace service accounts.
What is this MCP server?
- Personal Gmail via OAuth2 client ID, secret, and refresh token
- Google Workspace access via service account client email and PEM private key
- Stdio MCP transport run with npx (-y) from npm package gmail-workspace-mcp-server
- Supports both inbox automation workflows and customer-facing email agents
- Version 0.4.10 aligned with MCP server schema 2025-09-29
- Package version 0.4.10
- Stdio transport via npx
- Two auth modes: OAuth2 and service account
What problem does it solve?
Builders waste hours context-switching to Gmail when agents need thread context or outbound mail during product work.
Who is it for?
Indie builders automating founder inbox triage or embedding email actions in Claude Code agent workflows.
Skip if: Teams that need a full helpdesk, marketing ESP, or bulk cold-email platform without Google API setup.
What do I get? / Deliverables
After registration, your agent can query and act on Gmail through MCP tools with credentials kept in env vars.
- Registered Gmail MCP server in agent config
- Agent-callable Gmail tools over stdio transport
Recommended MCP Servers
Journey fit
How it compares
MCP Gmail bridge, not a standalone agent skill or email template pack.
Common Questions / FAQ
Who is com.pulsemcp/gmail for?
Solo and indie builders using Claude Code, Cursor, or Codex who want Gmail inside their agent toolchain.
When should I use com.pulsemcp/gmail?
When you are building or operating agent workflows that must read, search, or send mail from a Google account you control.
How do I add com.pulsemcp/gmail to my agent?
Add the stdio server via npx gmail-workspace-mcp-server, set OAuth or service-account env vars, and restart your MCP client.