Faithk7 Gmail Mcp
Automate Gmail read, send, label, and draft operations from your agent for support, onboarding, and ops scripts.
Overview
Gmail MCP is a MCP server for the Build phase that lets agents manage Gmail messages, threads, labels, drafts, and settings from workflows.
What is this MCP server?
- Manage messages, threads, labels, drafts, and mailbox settings via MCP tools
- Send and organize mail from agent-driven workflows instead of manual UI steps
- Smithery-hosted streamable HTTP with required Bearer Smithery API key
- Maintained Gmail MCP project on GitHub (faithk7/gmail-mcp) at version 1.7.4
- Suites indie operators who treat email as part of product and support automation
- Published server version 1.7.4 on Smithery
- Repository: github.com/faithk7/gmail-mcp
- One required secret header: Bearer smithery_api_key
What problem does it solve?
Copy-pasting between Gmail and your agent breaks flow when you need to send, label, or summarize threads during shipping or support.
Who is it for?
Founders automating founder inbox, support triage, or transactional email checks alongside coding agents.
Skip if: Enterprises needing full CRM replacement, strict DLP-only channels, or agents without Google API consent setup.
What do I get? / Deliverables
Mailbox actions become callable tools so your agent can draft, organize, and send mail as part of integrated build-and-operate workflows.
- Agent-callable send, draft, label, and thread management actions
- Reduced manual Gmail UI work during support and ops tasks
- Composable email steps inside larger agent workflows
Recommended MCP Servers
Journey fit
Email automation is wired into apps and internal tooling while you build workflows and connect services. Gmail MCP is a direct Google mailbox integration—exactly the kind of external API hook agents use during build.
How it compares
Gmail API MCP bridge, not a newsletter growth skill or inbox analytics dashboard.
Common Questions / FAQ
Who is Gmail MCP for?
Indie builders and small teams who use AI agents daily and want Gmail operations—send, label, draft, thread management—inside MCP workflows.
When should I use Gmail MCP?
Use it while building automations for support, onboarding, or ops mail, or when your agent must read and act on threads without opening the Gmail UI.
How do I add Gmail MCP to my agent?
Add the Smithery remote for @faithk7/gmail-mcp, configure Bearer {smithery_api_key}, complete any Google OAuth steps from the GitHub README, then connect streamable HTTP in your client.