# giuseppe-coco/Google-Workspace-MCP-Server [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/giuseppe-coco/Google-Workspace-MCP-Server  
**GitHub Stars:** 30  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/giuseppe-coco-google-workspace-mcp-server

## Description
MCP server that seamlessly interacts with your Google Calendar, Gmail, Drive and so on.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "google-workspace-mcp-server": {
    "command": "npx",
    "args": ["-y","giuseppe-coco-google-workspace-mcp-server"]
  }
}
```

## Documentation

## What the giuseppe-coco/Google-Workspace-MCP-Server MCP server does

The giuseppe-coco/Google-Workspace-MCP-Server MCP server provides MCP tools for working with Google Calendar, Gmail, and Google Drive from an authorized Google account. It is intended for use with MCP clients, with Claude Desktop shown as the example client in the project documentation.

Calendar capabilities include listing and searching events on the primary calendar within a date range, creating events with details such as title, description, and times, applying partial updates, and deleting events. Gmail tools can retrieve the latest email, search messages by subject, and compose and send a new message. Drive tools search for files and folders with query strings, create Google Docs with a title and starting content, replace the complete content of an existing Google Doc, and move files to the bin or delete them permanently.

## How it works

The giuseppe-coco/Google-Workspace-MCP-Server MCP server runs locally as a Python project and communicates with an MCP-compatible client. Google Cloud supplies the authorization layer. The setup requires a Google Cloud project with the Gmail, Google Calendar, and Google Drive APIs enabled, plus an OAuth client configured as a desktop application.

After the OAuth client JSON is downloaded and renamed to `client_secrets.json`, the included `get_credentials.py` script opens a browser for Google account consent. Once authorization is complete, it creates `token.json` in the project directory. The token allows subsequent runs to reuse the authorization rather than requiring a new browser login each time.

## Setup and configuration

Use Python 3.9 or newer and install `uv` or use `pip`. Clone the repository, create a virtual environment, activate it, and install the dependencies listed in `requirements.txt`. Place `client_secrets.json` in the repository root, then run `python get_credentials.py` to complete the one-time authorization.

For Claude Desktop, add an MCP server entry to its configuration file. The entry uses the Python executable from the project’s virtual environment as the command and the absolute path to `mcp_server.py` as its argument. The README gives a Windows configuration path and notes that other MCP clients can also be used.

## Tools and capabilities

The giuseppe-coco/Google-Workspace-MCP-Server MCP server supports these currently documented operations:

- Find, create, edit, and delete primary-calendar events.
- Read the newest email and search by subject.
- Send email from the connected Gmail account.
- Search Drive files and folders with Google query syntax.
- Create Google Docs and replace their full content.
- Move Drive items to the bin or delete them permanently.

The examples cover workflows such as turning email information into a calendar reminder, checking availability, drafting a trip document, changing a meeting time, searching for messages, and sending an email.

## Limitations and notes

The project currently focuses on the listed Calendar, Gmail, and Drive operations. The roadmap mentions more granular Google Docs editing, Google Sheets support, and additional features for the existing services, but those planned additions should not be treated as current capabilities. Google Cloud API enablement, OAuth consent configuration, and account authorization are required before the server can access Workspace data. Permanent Drive deletion is available alongside binning, so clients should distinguish between those actions when issuing requests.

_Full upstream README: https://allmcps.com/mcp/giuseppe-coco-google-workspace-mcp-server/readme_