1. Conduid
  2. AI
  3. Gmail MCP
MCP server · AI

Gmail MCP

MCP server providing read-only Gmail tools for AI assistants like Claude Code

Unclaimed MIT comms
39Low

Scored 20 days ago · breakdown

About Gmail MCP

Gmail MCP is an MCP server published by cafferychen777 in the AI category: mCP server providing read-only Gmail tools for AI assistants like Claude Code. It has been installed 0 times through Conduid.

Install

Install
npx gmail-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Gmail MCP

Powered by Claude · Grounded in docs

I know everything about Gmail MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

v0.1.1v0.1.1 – docs & community polish · 24 Aug 2025Changes in v0.1.1\n\nDocs & SEO\n- README: badges (stars, release, PRs, discussions, contributors, good-first-issues, issues, PRs), CTA, prerequisites, demo/screenshots section\n- Social preview: add placeholder at…
v0.1.0v0.1.0 - First public preview · 24 Aug 2025• One-command install via ./bin/gmail-mcp • Chrome extension + MCP bridge • Works with Claude Desktop, no API keys, free • Basic Gmail read/search/send/reply Docs: README.md

README

Gmail MCP Bridge

English | 中文文档 README.zh-CN.md

Control Gmail from Claude. No Google Cloud. No OAuth. No API keys.

Chrome Extension MCP Compatible GitHub Repo stars Website GitHub release (latest SemVer) PRs Welcome Discussions Contributors Good first issues Open issues Open PRs No Google Cloud / OAuth

Enable Gmail automation for AI assistants through a Chrome extension and the Model Context Protocol. Works locally, respects your browser session, and requires no Google API keys.

If this project helps you, please ⭐ star the repo and join the Discussions.

⚡️ Bold advantage: No Google Cloud project. No OAuth consent screen. No API keys. It uses your existing Chrome session to act in Gmail.

Why no Google Cloud

This project works locally by leveraging your existing Chrome browser session. The extension and MCP server act on Gmail the same way you do in the browser, so you do not need to set up a Google Cloud project, OAuth consent screen, or any API keys.

Benefits:

  • Simpler onboarding: no cloud console, no OAuth app review.
  • Privacy: actions stay within your local browser session.
  • Portability: works anywhere Chrome runs.

Limitations to note:

  • Requires Chrome to be installed and signed in to the target Gmail account.
  • Actions follow the permissions of your current Gmail session.

⚡ Installation

For a guided setup, see the Quick Start and Website:

Prerequisites:

  • Node.js 18+
  • Google Chrome (latest)
  • Claude Desktop (with MCP enabled)
# One-command install (recommended)
./bin/gmail-mcp install

# Or manual setup
cd gmail-mcp-extension/mcp-server && npm install

📁 Project Structure

gmail-mcp/
├── bin/                     # CLI utilities (installer/manager)
│   └── gmail-mcp
├── gmail-mcp-extension/     # Chrome Extension + MCP bridge server
│   ├── extension/           # Chrome extension source
│   ├── mcp-server/          # MCP bridge server
│   └── src/                 # Core logic and recovery system
├── docs/                    # Documentation
│   ├── planning/
│   ├── reports/
│   └── analysis/
├── scripts/                 # Tooling scripts
│   ├── test/
│   └── util/
├── src/                     # Advanced features
│   ├── core/
│   └── plugins/
├── tests/
├── tools/
└── Key docs
    ├── README.md
    ├── README.zh-CN.md
    ├── CLAUDE.md
    ├── CONTRIBUTING.md
    └── RELEASE.md

🚀 Features

  • Gmail read/search/send/reply
  • Full Gmail search syntax support
  • Multi-account switching
  • Auto-recovery (95%+ common failures)
  • Self-diagnosis and repair utilities
  • Low-latency, high-throughput local bridge

🎯 Usage

CLI management

gmail-mcp status    # Check system status
gmail-mcp doctor    # Diagnose issues
gmail-mcp fix       # Auto-fix common problems
gmail-mcp test      # Run tests

In Claude Desktop

After installation, just ask Claude:

  • "Check my latest emails"
  • "Send an email to john@example.com"
  • "Search emails containing 'project'"

📚 Documentation

🎬 Demo / Screenshots

Below are placeholder screenshots; a short demo GIF will be added soon.

Install

Claude command triggering Gmail tools

Gmail action executed

Planned: docs/assets/screenshots/demo.gif (≤10s).

If you'd like to help, check the good first issues.

🏆 Why this project

  • No API keys, works directly with your browser session
  • Fast local bridge with MCP for AI assistants
  • Production-ready structure with installer and diagnostics

🔗 Social preview (Open Graph)

Improve link previews when sharing the repo by uploading a social image:

  1. Use the placeholder at docs/assets/images/og-preview.svg (export to 1200×630 PNG if needed)
  2. Go to GitHub → Repository Settings → General → Social preview → Upload the image

🤝 Contributing

PRs welcome! Please read CONTRIBUTING.md.

📄 License

MIT License — see LICENSE


Gmail MCP Bridge — Control Gmail from Claude Desktop via MCP 🚀

🧭 Community & Support

README mirrored from the source repository 20 days ago. The original is authoritative.

Questions

About Gmail MCP

How do I install Gmail MCP?

Run npx gmail-mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Gmail MCP safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Gmail MCP still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.