Gmail MCP Server
Provides tools for searching, reading, sending, and organizing emails, managing labels, extracting addresses, and handling attachments through the Gmail API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Gmail MCP Serverfind emails from my boss about meeting"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
⚡ Quick Start
# One-command setup — auto-configures your AI client
npx gmail-mcp-server setupThat's it. The setup wizard will:
Check your Google OAuth credentials
Let you choose your AI client (Claude Desktop, Claude Code, Cursor, Windsurf)
Auto-write the config file
Run the OAuth authentication flow
✨ Why choose this MCP?
While Google provides workspace integrations and generic email readers exist, this MCP is explicitly built for AI Agents acting autonomously:
Zero-Config Setup:
npx gmail-mcp-server setupdetects your OS and AI client, automatically editing your local configuration JSON. No manual path mapping required.Built for AI Agents: Includes tools like
advanced_filter(search + bulk actions with LLM-friendly dry-runs),batch_modify_emails(modify 1000 emails at once), andget_frequent_contacts(turn an inbox into a CRM context).100% Local & Private: Bring-your-own-credentials. Tokens remain strictly on your machine. No proxy servers, no telemetry, and no third-party email routing.
Modular & Extensible: Clean, deeply typed domain-driven structure (e.g.,
src/tools/compose.ts,src/tools/search.ts) making it extremely easy for developers to fork and extend.
🔧 Tools (20 tools)
Category | Tool | Description |
Search |
| Search with Gmail query syntax ( |
Read |
| Full email content — body, headers, attachments |
| All messages in a thread | |
Compose |
| Send a new email |
| Reply (or reply-all) keeping the thread | |
| Forward with optional note | |
| Save a draft (optionally in a thread) | |
Organize |
| Add/remove labels, mark read/unread |
| Bulk modify up to 1000 emails | |
| Move to trash | |
| Restore from trash | |
| Bulk trash | |
| Mark as spam | |
| Search + bulk action (archive, label, etc.) with dry-run | |
Labels |
| List all labels with IDs |
| Create new label (supports nesting) | |
| Delete user-created label | |
Extract |
| Extract unique addresses from search results |
| Filter, sort, reformat email data | |
Profile |
| Your email address, message/thread counts |
| Most-contacted addresses from sent mail | |
Attachments |
| Download attachment content |
🚀 Step-by-Step Setup Guide
Follow these steps to get your Gmail MCP server running in less than 5 minutes.
1. Create Google Cloud Project & Enable API
Open the Google Cloud Console.
Create a New Project: Click the project dropdown (top left) → "New Project" → Name it
Gmail MCP→ "Create".Enable Gmail API: Search for "Gmail API" in the search bar → Click it → Click Enable.
2. Configure OAuth Consent Screen
Go to APIs & Services → OAuth consent screen.
Select User Type: "External" (or "Internal" if you have a Google Workspace) → Click Create.
App Information: Fill in "App name" (e.g.,
Gmail MCP) and "User support email".Developer Contact: Fill in your email address.
Click Save and Continue until you reach the Summary.
Add Test Users: Go back to the "OAuth consent screen" tab → Under "Test users" → Click + ADD USERS → Enter your Gmail address → Click Save.
3. Generate Credentials
Go to APIs & Services → Credentials.
Click + CREATE CREDENTIALS → Select OAuth client ID.
Application type: Select Desktop app.
Name: Give it a name (e.g.,
Gmail MCP Client).Click Create.
Download JSON: In the "OAuth 2.0 Client IDs" list, click the download icon (↓) for your new client.
Rename & Move: Save this file as
credentials.jsonin your project folder (or keep it ready for the setup wizard).
4. Run the Setup Wizard
Open your terminal and run:
npx gmail-mcp-server setupThe wizard will guide you through:
Finding your
credentials.json.Selecting your AI client (Claude, Cursor, etc.).
Authorizing the app via your browser.
🖥️ Client Configuration
Claude Desktop
npx gmail-mcp-server setup # Select "Claude Desktop"Or manually add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["-y", "gmail-mcp-server"]
}
}
}Claude Code
npx gmail-mcp-server setup # Select "Claude Code"Or add to ~/.claude/mcp.json:
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["-y", "gmail-mcp-server"]
}
}
}Cursor
npx gmail-mcp-server setup # Select "Cursor"Or add to .cursor/mcp.json:
{
"mcpServers": {
"gmail": {
"command": "npx",
"args": ["-y", "gmail-mcp-server"]
}
}
}Windsurf
npx gmail-mcp-server setup # Select "Windsurf"🛠️ CLI Commands
npx gmail-mcp-server setup # Interactive setup wizard
npx gmail-mcp-server auth # Run OAuth flow
npx gmail-mcp-server serve # Start MCP server (default)
npx gmail-mcp-server doctor # Diagnose issues
npx gmail-mcp-server --help # Show help
npx gmail-mcp-server --version # Show version🩺 Troubleshooting
If you run into issues, try the following:
Run the Doctor:
npx gmail-mcp-server doctorwill diagnose common problems with your credentials, tokens, and system.Missing
credentials.json: Ensure you've downloaded the file from Google Cloud Console and it's named exactlycredentials.jsonin your current directory.Invalid Grant / Expired Token: If the server can't connect, try running
npx gmail-mcp-server authto reset your OAuth tokens.Port 3000 Busy: The auth flow uses port 3000. If it's busy, the flow might fail. Ensure no other apps are using port 3000 during setup.
💬 Usage Examples
Once configured, ask your AI agent:
"Search my emails for unread messages from GitHub"
"Get the full content of email ID 18abc123"
"Show me the whole thread for this conversation"
"Reply to that email saying thanks"
"Forward the invoice to accounting@company.com"
"Create a draft reply for that message"
"Mark all newsletters from last month as read"
"Extract all email addresses from my last 50 emails"
"Who do I email most frequently?"
"Download the PDF attachment from that email"
🔒 Security
credentials.json— never committed (in.gitignore)Tokens stored in
~/.gmail-mcp/token.json— outside the project, auto-refreshedOAuth scope:
gmail.modify(read + modify, no permanent delete or admin)All data stays local — no external servers, no telemetry
🌍 Environment Variables
Variable | Default | Description |
|
| Path to your OAuth credentials file |
|
| Base directory for credentials lookup |
🤝 Contributing
We welcome contributions! See CONTRIBUTING.md for guidelines.
git clone https://github.com/neutral-Stage/gmail-mcp-server.git
cd gmail-mcp-server
npm install
npm run build📄 License
MIT — use it however you want.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/neutral-Stage/gmail-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server