Gmail

io.github.mcp-zPublished by GitHub account mcp-zv2.3.3Updated Oct 24, 2026

Gmail integration with OAuth authentication, message search, batch operations, and Sheets export

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant read and search Gmail messages, run batch operations, and export results to Google Sheets via OAuth.

What you can do
This local MCP server connects an assistant to Gmail. According to its registry description, it provides Gmail integration with OAuth authentication, message search, batch operations, and Sheets export. It runs as a local process over stdio, typically started with npx from the npm package.
When to use it
Worth adding when an assistant needs to search or work with Gmail messages and move results into Google Sheets, and when you are comfortable configuring Google OAuth credentials on your own machine.
Requirements
A local Node.js runtime to run the npm package via npx. Google OAuth credentials: GOOGLE_CLIENT_ID is required, and GOOGLE_CLIENT_SECRET is a secret used for OAuth modes. Alternatively a service account JSON key file path (GOOGLE_SERVICE_ACCOUNT_KEY_FILE). Several optional variables configure auth mode, HTTP transport, DCR, redirect URI, port, and logging. Desktop only; no web executable.
Before you install
Requires Google account credentials: GOOGLE_CLIENT_ID and the secret GOOGLE_CLIENT_SECRET, or a service account key file, which grant access to your Gmail data. Batch operations and Sheets export may read, write, or change data in your Google account. Review the requested OAuth scopes before authorizing.

Installation

In SourceWeft

  1. Open Gmail in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v2.3.3LatestOct 12, 2026
  2. v2.3.2Oct 10, 2026
  3. v2.3.1Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.