# google-mcp-suite [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/simiancraft/google-mcp-suite  
**GitHub Stars:** 5  
**npm Downloads (last month):** 1436  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/google-mcp-suite

## Description
Google Workspace MCP servers for AI agents, one per service per account: Gmail, Google Calendar, Google Drive, Google Docs, and Google Sheets. Identity is bound to the running instance, so an agent (Claude, Cursor, or any MCP client) can never act on the

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "google-mcp-suite": {
    "command": "npx",
    "args": ["-y","google-mcp-suite"],
    "env": {
      "GOOGLE_MCP_ACCOUNT": ""
    }
  }
}
```

**Requires environment variables:** `GOOGLE_MCP_ACCOUNT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What google-mcp-suite does

google-mcp-suite MCP server connects AI agents to Google Gmail, Calendar, Drive, Docs, and Sheets. The package provides one service-specific server per account, allowing an agent to triage or send mail, manage calendar data, edit documents and spreadsheets, and work with files or shared drives.

The package includes 210 operations: 33 for Gmail, 31 for Calendar, 35 for Drive, 35 for Docs, and 76 for Sheets. Gmail, Calendar, and Drive include curated MCP operations alongside broader REST methods. Docs and Sheets are sourced entirely from their REST references because Google had not published MCP toolsets for those services when these servers shipped.

Identity is attached to the running server process rather than supplied with each call. This lets separate instances represent different accounts and prevents a request sent to one instance from acting as another account. Each Google service also runs independently, with the orchestrating agent responsible for coordinating them.

## How it works

Each operation follows the same internal structure: a schema, handler, index, and test file. The server function registers these operations as MCP tools. Google’s tool-list and REST method references determine the operation layout, vocabulary, and available capabilities.

The google-mcp-suite MCP server validates request inputs and returned data against schemas on every call. Operations are exposed over the MCP wire protocol, so an MCP-compatible client can launch the service-specific binaries. The package also includes a host process that serves every service and account through one Streamable HTTP process.

## Setup and configuration

Install the package globally with npm, then use the included doctor command to identify the Google APIs and scopes to enable in Google Cloud. A Google Cloud OAuth client is required. The authentication command opens browser consent and stores a token for the selected account; repeat it for each account you intend to use.

Configure an MCP client with the relevant binary, such as `google-mcp-gmail` or `google-mcp-calendar`, and set `GOOGLE_MCP_ACCOUNT` to the account represented by that instance. The same service can be configured multiple times with different account values. Run `google-mcp-doctor` to check provisioning, authorization, and reachability.

The package also provides a front-door command, so service selection can be dispatched with commands such as `npx google-mcp-suite gmail` or `npx google-mcp-suite host`.

## Tools and capabilities

- Gmail mail triage and sending
- Google Calendar operations
- Google Drive file and shared-drive management
- Google Docs document operations
- Google Sheets spreadsheet operations
- Curated MCP tools and broader REST methods in one surface
- Separate account-bound instances running in parallel

## Limitations and notes

google-mcp-suite MCP server requires Google Cloud provisioning and account authorization before use. Access is separated by running instance and service; the agent must connect to each required service and account explicitly. The repository describes the package as MIT licensed and pins test coverage at 100%, but the available material does not define service-specific Google API quotas or permission behavior.

This package is listed in the Workplace & Productivity category and is intended for MCP clients that can launch standard MCP processes or connect through the provided Streamable HTTP host.

_Full upstream README: https://allmcps.com/mcp/google-mcp-suite/readme_