AgentHubAgentHub

google-mail MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.mmedum/google-mail-mcp · v2.0.4

Gmail over MCP from your own account: search, read threads and messages, labels and drafts.

View on MCP Registry ↗Repository ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Gmail over MCP from your own account: search, read threads and messages, labels and drafts. google-mail-mcp is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

Code review & GitHubCursor essentials

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-10-04
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.
No auto-generated install guide — see the source repository README.

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for google-mail-mcp

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for google-mail-mcp?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Tool calls timing out or failing to download packages?

First-time package downloading might be slow or timeout due to network limits. Configure a reliable mirror or check outbound proxy settings.

Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

google-mail-mcp Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: google_mail_mcpExecute the core tool interface of google-mail-mcp
Request ArgumentsJSON Schema
{
  "target": "google-mail-mcp",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

google-mail-mcp + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: google-mail-mcp
HTML
<a href="https://myagenthub.cn/p/io.github.mmedum/google-mail-mcp" title="Listed on AgentHub: google-mail-mcp" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.mmedum/google-mail-mcp?lang=en" alt="Listed on AgentHub: google-mail-mcp" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: google-mail-mcp](https://myagenthub.cn/badge/io.github.mmedum/google-mail-mcp?lang=en)](https://myagenthub.cn/p/io.github.mmedum/google-mail-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.mmedum/google-mail-mcp",
  "type": "mcp-server",
  "version": "2.0.4",
  "displayName": "google-mail-mcp",
  "description": "Gmail over MCP from your own account: search, read threads and messages, labels and drafts.",
  "repository": {
    "url": "https://github.com/mmedum/google-mail-mcp",
    "source": "github"
  },
  "homepage": "https://github.com/mmedum/google-mail-mcp#readme",
  "distribution": {
    "packages": [
      {
        "registryType": "mcpb",
        "identifier": "https://github.com/mmedum/google-mail-mcp/releases/download/v2.0.4/google-mail-mcp_2.0.4.mcpb",
        "version": "2.0.4",
        "transport": "stdio"
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.mmedum/google-mail-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.mmedum%2Fgoogle-mail-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}