com.pulsemcp/gmail

MCP server for Gmail with OAuth2 (personal) and service account (Workspace) support.

com.pulsemcp/gmail · Repository · version 0.4.11 · 77 stars · listed from registry

Install

The sweep installs into a clean prefix, but this is the command a user would run:

npx gmail-workspace-mcp-server

Results by platform

Linux

MCP handshake failed2026-08-16 · probed over npm

2 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[ERROR] validateEnvironment: Missing required environment variables:

This MCP server supports two authentication modes:

--- Option 1: OAuth2 (for personal Gmail accounts) ---
  GMAIL_OAUTH_CLIENT_ID: OAuth2 client ID from Google Cloud Console
  GMAIL_OAUTH_CLIENT_SECRET: OAuth2 client secret
  GMAIL_OAUTH_REFRESH_TOKEN: Refresh token from one-time consent flow

  Setup: Run `npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>`

--- Option 2: Service Account (for Google Workspace) ---
  GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL: Service account email address
    Example: [email protected]
  GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY: Service account private key (PEM format)
    Example: -----BEGIN PRIVATE KEY-----\nMIIE...\n-----END PRIVATE KEY-----
  GMAIL_IMPERSONATE_EMAIL: Email address to impersonate
    Example: [email protected]

  Setup steps:
  1. Go to https://console.cloud.google.com/
  2. Create a service account with domain-wide delegation
  3. In Google Workspace Admin, grant required Gmail API scopes
  4. Download the JSON key file and extract client_email and private_key

Optional environment variables:
  GMAIL_ENABLED_TOOLGROUPS: Comma-separated list of tool groups to enable
    Valid groups: readonly, readwrite, readwrite_external
    Default: all groups enabled
    Example: GMAIL_ENABLED_TOOLGROUPS=readwrite

======================================================

macOS

MCP handshake failed2026-08-16 · probed over npm

2 recorded runs, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[ERROR] validateEnvironment: Missing required environment variables:

This MCP server supports two authentication modes:

--- Option 1: OAuth2 (for personal Gmail accounts) ---
  GMAIL_OAUTH_CLIENT_ID: OAuth2 client ID from Google Cloud Console
  GMAIL_OAUTH_CLIENT_SECRET: OAuth2 client secret
  GMAIL_OAUTH_REFRESH_TOKEN: Refresh token from one-time consent flow

  Setup: Run `npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>`

--- Option 2: Service Account (for Google Workspace) ---
  GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL: Service account email address
    Example: [email protected]
  GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY: Service account private key (PEM format)
    Example: -----BEGIN PRIVATE KEY-----\nMIIE...\n-----END PRIVATE KEY-----
  GMAIL_IMPERSONATE_EMAIL: Email address to impersonate
    Example: [email protected]

  Setup steps:
  1. Go to https://console.cloud.google.com/
  2. Create a service account with domain-wide delegation
  3. In Google Workspace Admin, grant required Gmail API scopes
  4. Download the JSON key file and extract client_email and private_key

Optional environment variables:
  GMAIL_ENABLED_TOOLGROUPS: Comma-separated list of tool groups to enable
    Valid groups: readonly, readwrite, readwrite_external
    Default: all groups enabled
    Example: GMAIL_ENABLED_TOOLGROUPS=readwrite

======================================================

Windows

MCP handshake failed2026-08-16 · probed over npm

1 recorded run, oldest first.

handshake failed: MCP error -32000: Connection closed
--- stderr (tail) ---
[ERROR] validateEnvironment: Missing required environment variables:

This MCP server supports two authentication modes:

--- Option 1: OAuth2 (for personal Gmail accounts) ---
  GMAIL_OAUTH_CLIENT_ID: OAuth2 client ID from Google Cloud Console
  GMAIL_OAUTH_CLIENT_SECRET: OAuth2 client secret
  GMAIL_OAUTH_REFRESH_TOKEN: Refresh token from one-time consent flow

  Setup: Run `npx gmail-workspace-mcp-server oauth-setup <client_id> <client_secret>`

--- Option 2: Service Account (for Google Workspace) ---
  GMAIL_SERVICE_ACCOUNT_CLIENT_EMAIL: Service account email address
    Example: [email protected]
  GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY: Service account private key (PEM format)
    Example: -----BEGIN PRIVATE KEY-----\nMIIE...\n-----END PRIVATE KEY-----
  GMAIL_IMPERSONATE_EMAIL: Email address to impersonate
    Example: [email protected]

  Setup steps:
  1. Go to https://console.cloud.google.com/
  2. Create a service account with domain-wide delegation
  3. In Google Workspace Admin, grant required Gmail API scopes
  4. Download the JSON key file and extract client_email and private_key

Optional environment variables:
  GMAIL_ENABLED_TOOLGROUPS: Comma-separated list of tool groups to enable
    Valid groups: readonly, readwrite, readwrite_external
    Default: all groups enabled
    Example: GMAIL_ENABLED_TOOLGROUPS=readwrite

======================================================

Badge

Paste this into the project README to show the current result:

[![does it install](https://img.shields.io/endpoint?url=https://doesitinstall.com/badge/com.pulsemcp__gmail.json)](https://doesitinstall.com/s/com.pulsemcp__gmail.html)