Skip to main content
Glama

GSuite MCP Lane — Gmail search + Sheets append as MCP tools

Two scoped MCP tools that move seller-inbox rows from Gmail into Google Sheets without Zapier: gold_gmail_search + gold_sheets_append. BYOK Google OAuth, no hosted sync, no stored credentials.

Portfolio showcase extracted from private studio work. Derivative of MarkusPfundstein/mcp-gsuite (MIT, 489★) — original license preserved in THIRD_PARTY_NOTICES.md.

Scope: the tools return honest config_needed stubs and wiring plans until Google OAuth is connected — no data is ever invented. Wire googleapis calls to go fully live.

Tools

Tool

What it does

gold_gmail_search

Search Gmail by query (newer_than:7d seller/order/refund default). Returns {id, threadId, snippet}. Without auth returns an honest config_needed stub — never invented data.

gold_sheets_append

Append [[col1,col2],...] rows to spreadsheet_id / sheet_name. Returns config_needed without auth.

All tools are gold_* prefixed — no collision with upstream mcp-gsuite. A guided 2-step (search then append) lives in src/moat.ts; the 2 granular tools are the primary contract.

Example (without auth — preview):

// gold_gmail_search { "query": "newer_than:7d", "max_results": 20 }
// → { "tool":"gold_gmail_search", "query":"newer_than:7d", "status":"config_needed", "hint":"Set GOOGLE_OAUTH_..." }

// gold_sheets_append { "spreadsheet_id":"1Bxi...","values":[["2026-08-22","order #123","$19"]]}

Related MCP server: charity-gmail-mcp

Quickstart

npm install
npm run build
node dist/index.js

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "gsuite-mcp-lane": {
      "command": "node",
      "args": ["/absolute/path/to/gsuite-mcp-lane/dist/index.js"],
      "env": {
        "GOOGLE_OAUTH_CLIENT_ID": "xxx.apps.googleusercontent.com",
        "GOOGLE_OAUTH_CLIENT_SECRET": "xxx",
        "GOOGLE_OAUTH_REFRESH_TOKEN": "xxx"
      }
    }
  }
}

BYOK setup (Google OAuth — no hosted sync)

  1. Google Cloud project → enable Gmail API + Google Sheets API.

  2. Create OAuth 2.0 Client ID → CLIENT_ID + CLIENT_SECRET.

  3. Generate a refresh token (offline access) → REFRESH_TOKEN (or short-lived ACCESS_TOKEN).

Var

Purpose

GOOGLE_OAUTH_CLIENT_ID

OAuth client ID

GOOGLE_OAUTH_CLIENT_SECRET

OAuth client secret

GOOGLE_OAUTH_REFRESH_TOKEN

Long-lived refresh token (preferred)

GOOGLE_OAUTH_ACCESS_TOKEN

Short-lived access token (alt)

GOOGLE_APPLICATION_CREDENTIALS

Service-account JSON path (alt)

Upstream attribution

Derivative code in src/ is original work. Upstream MIT preserved in THIRD_PARTY_NOTICES.md.

Stack

TypeScript · MCP SDK (stdio) · zod schemas · BYOK OAuth

Next steps

Drive/Calendar tools from the same upstream, write-path confirmations, Smithery registry listing.

License

MIT, Copyright 2026 Maxim Konovalov. See LICENSE.

Author

Maxim Konovalov — Haifa · MCP servers + AI pipelines. More lanes + private demos on call.

Available Tools

3 tools
gold_setup_checkA

SETUP CHECK for GSuite MCP Lane — run this FIRST. Shows license tier, which API keys are set vs missing (names only, never values), and the exact next step.

Inputs: no named parameters.

gold_sheets_appendB

Google Sheets append rows (BYOK Google OAuth). Append [[col1,col2]] to spreadsheetId. No hosted sync.

Inputs: values (required), spreadsheet_id (required), range, sheet_name.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: setup check, Gmail search, and Sheets append. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share a consistent gold_ prefix and use verb_noun naming (setup_check, gmail_search, sheets_append). Minor inconsistency: gmail_search and sheets_append are resource_action while setup_check is action_noun, but the pattern is still predictable.

    Tool Count3/5

    Three tools is on the low end but reasonable for a narrowly scoped GSuite lane focused on setup, Gmail search, and Sheets append. It feels slightly thin but not inappropriate.

    Completeness2/5

    The server covers only a small slice of GSuite: setup check, Gmail search, and Sheets append. Obvious gaps include Gmail read/send, Sheets read/update, and any Drive or Calendar operations, so agents would hit dead ends for common workflows.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables accessing Gmail tools (search, read, draft) for a specific Google account via MCP, designed as a custom connector for Claude/Cowork to use alongside a different Google account.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Integrates with the Gmail API to send and read emails through MCP tools using Google OAuth authentication.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Gmail operations like listing, searching, sending emails, and managing labels via MCP tools.
      127 npm
      MIT