Gmail MCP Server

Multi-Account Gmail for AI Agents & Assistants

An open-source Model Context Protocol (MCP) server that gives AI agents and assistants full read and write access to Gmail. Connect multiple Gmail accounts, search emails, archive, label, and auto-unsubscribe. All through one server.

Works with Claude, OpenClaw, Cursor, Windsurf, Cline, Continue, and any MCP-compatible client.

Why This Exists

Most AI tools ship with a Gmail integration that can only read emails from a single account. No archiving. No labeling. No unsubscribing. And if you use multiple Gmail accounts? You're out of luck.

This MCP server fixes that. One server, all your accounts, full read and write access.

Gmail MCP Server vs Built-in Connectors

What is an MCP Server?

Model Context Protocol (MCP) is an open standard that lets AI agents and assistants connect to external tools and data sources. An MCP server exposes tools that any compatible client can call. Think of it as a plugin system for AI.

This Gmail MCP server turns any MCP-compatible AI client into a full-featured email agent.

Gmail MCP Server Features

• Multi-account support. Connect multiple Gmail accounts and switch between them, or query all at once.
• Full read and write access. Not just reading emails. Archive, label, modify, and unsubscribe.
• Gmail search syntax. Use Gmail's query language: is:unread, from:, newer_than:7d, has:attachment, and more.
• Auto-unsubscribe. Finds and triggers unsubscribe links automatically. Supports List-Unsubscribe headers, mailto links, and body link scanning.
• Batch operations. Fetch batches of emails for AI-powered triage and bulk actions.
• Secure by design. OAuth 2.0 authentication, AES-256-GCM encrypted token storage, minimal Gmail scopes.
• Deploy anywhere. Vercel (free), Railway, Docker, or your own server.

Available Tools

Setup Guide: Deploy in 5 Minutes

Prerequisites

1. A Google Cloud project with the Gmail API enabled
2. OAuth 2.0 credentials (Web application type)
3. A hosting platform (Railway, your own server, or Docker)

Step 1: Google Cloud Setup

1. Go to Google Cloud Console and create a new project
2. Enable the Gmail API (APIs & Services → Library → search "Gmail API" → Enable)
3. Configure the OAuth consent screen:
   • User type: External
   • Add scopes: gmail.readonly, gmail.modify
   • Add your Gmail addresses as test users
4. Create OAuth credentials:
   • APIs & Services → Credentials → Create Credentials → OAuth client ID
   • Application type: Web application
   • Authorized redirect URI: https://your-server-url/oauth/callback
   • Save the Client ID and Client Secret

Step 2: Deploy

Option A: Deploy to Vercel (free)

1. Import this repo in Vercel. vercel.json sets the Express preset
2. In the project, go to Storage and add Upstash for Redis (free plan). This sets KV_REST_API_URL and KV_REST_API_TOKEN, which is where connected accounts are saved (Vercel's disk does not persist)
3. Add the environment variables from the table below, with SERVER_URL set to https://<project>.vercel.app and no PORT
4. Add https://<project>.vercel.app/oauth/callback as an Authorized redirect URI in Google Cloud Console
5. Deploy

Option B: Deploy to Railway

1. Click the Deploy button above, or create a new project on Railway connected to this repo
2. Add these environment variables:

1. Generate a domain in Railway (Service → Settings → Networking → Generate Domain)
2. Update SERVER_URL with the generated domain
3. Update the Authorized redirect URI in Google Cloud Console to https://your-domain.railway.app/oauth/callback

Option C: Self-Host

git clone https://github.com/navbuildz/gmail-mcp-server.git
cd gmail-mcp-server
npm install
cp .env.example .env
# Edit .env with your values
npm run build
npm start

Option D: Docker

docker build -t gmail-mcp-server .
docker run -p 3000:3000 \
  -e GOOGLE_CLIENT_ID=your-client-id \
  -e GOOGLE_CLIENT_SECRET=your-client-secret \
  -e ENCRYPTION_KEY=your-random-string \
  -e ADMIN_PASSWORD=your-password \
  -e SERVER_URL=https://your-domain.com \
  gmail-mcp-server

Step 3: Connect Gmail Accounts

1. Visit https://your-server-url/setup
2. Enter your admin password
3. Click + Add Gmail Account
4. Sign in with Google and grant permissions
5. Repeat for each Gmail account you want to connect

Railway users without Redis: After adding accounts, copy the TOKENS_DATA= value from the server logs and add it as an environment variable in Railway. This keeps your accounts connected across redeploys.

How to Connect Gmail MCP Server to Claude

1. Go to Claude → Settings → Connectors
2. Click + → Add custom connector
3. Fill in:
   • Name: Gmail (or any name you prefer)
   • Remote MCP server URL: https://your-server-url/mcp/<MCP_SECRET> (choose "No sign-in"; the secret in the path is the credential)
   • Leave OAuth fields blank
4. Click Add
5. Start a new conversation and try: "List my connected Gmail accounts"

How to Connect Gmail MCP Server to Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "gmail": {
      "url": "https://your-server-url/mcp/<MCP_SECRET>"
    }
  }
}

How to Connect Gmail MCP Server to Windsurf

Add to your Windsurf MCP configuration:

{
  "mcpServers": {
    "gmail": {
      "serverUrl": "https://your-server-url/mcp/<MCP_SECRET>"
    }
  }
}

Multi-Account Gmail Setup

Connect as many Gmail accounts as you need. Every tool accepts an account parameter:

• Use a specific email: "account": "[email protected]"
• Query all accounts at once: "account": "all"

Example prompts you can try:

• "Show me unread emails from the last 2 days across all accounts"
• "Archive all promotional emails in [email protected]"
• "Unsubscribe from newsletters in all accounts"
• "Find emails with attachments from the last week in [email protected]"

Auto-Unsubscribe from Newsletters with AI

The unsubscribe_email tool handles the entire unsubscribe process:

1. Checks the List-Unsubscribe header (RFC 8058 one-click POST)
2. Tries HTTP unsubscribe links from the header
3. Sends an unsubscribe email via mailto: links
4. Scans the email body for unsubscribe URLs
5. Returns manual links if automatic unsubscribe isn't possible

Try it: "Find newsletters from the last month and unsubscribe from all of them"

Supported MCP Clients

Architecture

AI Agent / Assistant (Claude, OpenClaw, Cursor, Windsurf, Cline)
  ↓ MCP Protocol (Streamable HTTP)
Gmail MCP Server (Vercel / Railway / Self-hosted / Docker)
  ├── /mcp/<secret>    MCP endpoint (tools)
  ├── /setup           Admin page (add/remove accounts)
  ├── /oauth/callback  Google OAuth callback
  └── Token Store      Encrypted refresh tokens (Upstash Redis, or a file)
        ↓
Gmail API (per-account OAuth tokens)

Security

• OAuth 2.0 for authentication with Google
• AES-256-GCM encrypted refresh token storage
• Minimal scopes using only gmail.readonly and gmail.modify
• No passwords stored. Your Gmail password never touches the server
• Secret MCP endpoint. /mcp/<MCP_SECRET> is the only way in; anyone with that URL can use every tool, so treat it like a password
• Sending is explicit. create_draft never sends; send_email does, immediately. Set send_email to require approval in your MCP client if you want a confirmation step
• Password-protected setup. The /setup page requires admin authentication
• Revocable anytime from Google Account Permissions

Gmail Search Query Examples

The list_emails and batch_process tools accept Gmail's full search syntax:

Contributing

Want to help make this better? Here are some open ideas:

• Add send_email tool for composing and sending emails
• Add reply_to_email tool
• Add email attachment download support
• Add delete_email tool
• Add mark_as_read / mark_as_unread tools
• Add remove_label tool
• Add support for Google Workspace accounts

PRs are welcome. See CONTRIBUTING.md for guidelines.

Tech Stack

• Runtime: Node.js 20+
• Language: TypeScript
• MCP SDK: @modelcontextprotocol/sdk
• Gmail API: googleapis
• HTTP: Express 5
• Auth: Google OAuth 2.0

License

MIT

If this project is useful to you, give it a star. It helps others find it.