Skip to main content
Glama
Google Workspace MCP Server

Google Workspace MCP Server

by sahildhurat

Google Workspace MCP Server (Gmail + Google Docs)

A Model Context Protocol (MCP) server that exposes Google Workspace capabilities — specifically Gmail and Google Docs — as standardized MCP tools.

Features

  • send_email: Send an email immediately via the authenticated Gmail account.

  • draft_email: Create a draft in the authenticated Gmail account without sending.

  • append_to_google_doc: Append text content to the end of an existing Google Doc.

Related MCP server: Google Workspace MCP Server

Setup Instructions

1. Google Cloud Project Setup

  1. Go to the Google Cloud Console.

  2. Create a new project or select an existing one.

  3. Navigate to APIs & Services > Library.

  4. Search for and enable the Gmail API and Google Docs API.

  5. Navigate to APIs & Services > OAuth consent screen.

    • Configure the consent screen (External or Internal).

    • Add the following scopes:

      • https://www.googleapis.com/auth/gmail.send

      • https://www.googleapis.com/auth/gmail.compose

      • https://www.googleapis.com/auth/documents

    • Add your email address as a Test User if your app is in testing mode.

  6. Navigate to APIs & Services > Credentials.

    • Click Create Credentials > OAuth client ID.

    • Choose Desktop app as the application type.

    • Click Create.

    • Download the JSON file and rename it to credentials.json. Place it in the root of this project.

2. Environment Setup

  1. Copy .env.example to .env (optional, as defaults are used if not provided).

  2. Install the project dependencies:

    pip install -e .

3. First Run (Authentication)

Before an MCP client can use the server, you must authenticate it manually to generate the token.json file.

Run the server directly:

gmail-docs-mcp

This will open a browser window asking you to log in with your Google account and grant the requested permissions. Once completed, a token.json file will be created. You can then stop the server (Ctrl+C).

4. MCP Client Configuration

Configure your MCP client (e.g., Claude Desktop) to run this server. Add the following to your MCP client's configuration file:

{
  "mcpServers": {
    "google-workspace": {
      "command": "gmail-docs-mcp",
      "env": {
        "GOOGLE_CREDENTIALS_PATH": "/absolute/path/to/credentials.json",
        "GOOGLE_TOKEN_PATH": "/absolute/path/to/token.json"
      }
    }
  }
}

Note: Make sure to use absolute paths for the credentials and token files.

Testing

Run unit tests with pytest:

pip install -e ".[dev]"
pytest

Manual Smoke-Test Checklist

  1. Send test email: Invoke send_email with your own email address to verify receipt.

  2. Create draft: Invoke draft_email and check your Gmail Drafts folder.

  3. Append to a doc: Create a test Google Doc, copy its URL or ID, and invoke append_to_google_doc. Check the document to verify the text was appended at the end.

Available Tools

3 tools
append_to_google_docB

Append text content to the end of an existing Google Doc.

Inputs: content (required), document_id (required), leading_newline, add_timestamp_heading.

draft_emailB

Create a draft in the authenticated Gmail account without sending.

Inputs: to (required), body (required), subject (required), cc, +2 more.

send_emailB

Send an email immediately via the authenticated Gmail account.

Inputs: to (required), body (required), subject (required), cc, +2 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: append_to_google_doc targets Google Docs, while draft_email and send_email target Gmail with different actions (create draft vs send). No overlap exists between the three tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case: append_to_google_doc, draft_email, send_email. The pattern is predictable and uniform across the set.

    Tool Count2/5

    At 3 tools for a 'Google Workspace MCP Server,' the count feels too low. The server name suggests broader coverage of multiple Google Workspace services, but only Docs (append) and Gmail (draft/send) are represented, making the scope overly narrow.

    Completeness1/5

    The toolset is severely incomplete for Google Workspace. Key operations like creating or reading Google Docs, listing emails, managing labels, or handling attachments are missing. Agents cannot perform basic CRUD workflows for either Docs or Gmail.

    Related MCP Connectors

    • Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.

      https://www.primitive.dev/mcp
    • Email for AI agents: send, receive with a safety verdict, reply and approve, as MCP tools.

      https://mcp.oveyon.com/v1
    • Permissioned access to Gmail, Drive and Calendar via the user's own Google account

    • Your agent needs a mailbox of its own — to receive, thread, draft and send, with attachments, without borrowing your personal inbox or your company's SMTP. **What you can ask for** • "Create an inbox for this agent and tell me its address." • "Read the new messages in this thread and draft a reply." • "Send this message with the attachment and wait for the response." • "Search this inbox for everything from that domain." • "Show delivery metrics and the events on this inbox." **How to use it** Point any MCP client at https://mcp.aisa.one/mail/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: create and delete inboxes, list and read messages, raw message bodies, attachments, threads, drafts and draft attachments, send and reply, message search, inbox events, metrics, and list entries — reads and writes. **Why this rather than the source** A real inbox an agent owns, rather than an SMTP credential it borrows from a human. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the contact elsewhere in the catalogue, then write to them from here — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp finds the person to write to.

    Related MCP Servers