Happy slice of mcp pizzaMCP.pizza

Gmail-MCP-Server

MCP.Pizza Chef: ArtyMcLabin

This actively maintained fork handles everyday Gmail chores: sending messages with attachments, replying inside the correct thread, replying to everyone, saving attachments to your computer, creating and updating drafts before sending them, searching, labelling, and reporting phishing. You approve access with your Google account once and it stays signed in between restarts, and you can grant only the permissions you want. Permanent deletion stays off unless you deliberately turn it on. It runs locally rather than on someone else's server.

Communication
Email

Use This MCP server To

Send an email with an attachment without leaving the chat Reply so my message lands in the right thread Reply to everyone without rebuilding the recipient list Search my inbox and summarize what needs an answer Save an attachment from an email to my computer Draft an email now and send it later Report a suspicious message as phishing

README

Gmail MCP Server

Gmail MCP Server (Actively Maintained Fork)

Installation: npx @artymclabin/gmail-mcp auth - or just tell your Claude to install the MCP from this repo (https://github.com/ArtyMcLabin/Gmail-MCP-Server) and let it set up. Prefer manual steps? See Installation & Authentication.

CI npm

Also on the official MCP Registry (io.github.ArtyMcLabin/Gmail-MCP-Server) and Smithery.

This is an actively maintained fork of GongRzhe/Gmail-MCP-Server.

The original repository has been unmaintained since August 2025 - 7+ months with zero maintainer activity and 72+ unmerged pull requests. I use this MCP server daily as part of my Claude Code workflow and depend on it working correctly, so I picked it up.

Pull requests are welcome. If you've been sitting on fixes or features with nowhere to submit them, this is the place.

Philosophy

This fork is lean and pragmatic. It's a local stdio MCP server - you run it on your own machine, and your LLM client already has shell + filesystem access. So the threat model is "don't leak credentials to third parties, don't break the Gmail surface" - not "defend a hosted multi-tenant service". I keep dependencies minimal. I use this daily in my own Claude Code workflow - if I wouldn't run it or maintain it myself, it doesn't go in.

There's a downstream fork that took this in the maximalist direction. I'm not affiliated with its maintainer and I don't track its security or features - use it at your own risk: klodr/gmail-mcp. If that's the philosophy you want, go check it out. PRs welcome here as always.

What this fork adds

Gmail-MCP-Server FAQ

Can I use this to send email from my assistant?
Yes — you can send new messages with attachments, reply within a thread, or reply to everyone on it.
Which app does it work in?
It is written for Claude Desktop, and works with other assistants that support the same open standard.
Do I have to sign in to Google?
Yes. You approve access once with your Google account, and the sign-in survives restarts instead of expiring hourly.
How hard is setup?
One command runs the sign-in step, or you can point your assistant at the repository and let it set things up.
Can it delete my email by accident?
Permanent deletion requires you to opt in to a wider permission, so a default setup cannot do it.
Does my mail go through someone else's server?
No. It runs locally on your own machine.
Is this the original project?
It is a maintained fork of an earlier Gmail connector that had gone quiet, with threading, draft, and security fixes added.