Allows searching and reading emails and threads, managing labels, attachments, and drafts, as well as sending messages and replies.
Enables managing calendars, searching and reading events, checking availability, and creating or updating events.
Enables creating documents, reading document structure and text, and inserting or replacing content.
Allows searching for files, accessing metadata and folder contents, and uploading or exporting files.
Provides tools for reading and writing spreadsheet ranges, accessing table metadata, and performing batch operations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@google-workspace-mcp Find the latest email from my manager about the Q3 budget and summarize it"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A project for building five independent remote MCP servers for Google Workspace: Gmail, Google Calendar, Google Drive, Google Sheets, and Google Docs.
Status: pre-alpha. The MCP servers are not operational yet. The repository currently contains the package scaffold, five placeholder entry points, the downstream OAuth state core, and immutable per-service configuration.
Implemented:
a Python package with five console entry points;
SQLite-backed downstream OAuth state;
OAuth client registration and PKCE;
token binding to a canonical resource;
refresh token rotation, replay detection, and family revocation;
immutable state ownership metadata for the service and resource;
immutable per-service configuration with strict port and token TTL validation.
All five console entry points are placeholders and exit with a message that the service is not built. The HTTP/MCP transport, Google API integration, service tools, and deployment configuration are not implemented yet.
Related MCP server: google-workspace-mcp-advanced
The table describes the target scope. These capabilities are not available yet.
Service | Target capabilities |
| search and read messages and threads, labels, attachments, drafts, send, and reply |
| calendars, event search and retrieval, availability, event creation and updates |
| file search, metadata, folder contents, download, and export |
| spreadsheet metadata, range reads and writes, batch operations |
| document creation, structure and text retrieval, insert, and replace |
In the target architecture, each service runs as a separate process with its own MCP endpoint, tool registry, Google OAuth scopes, Google credentials, and downstream OAuth state.
The design uses two independent layers:
Client to service. The MCP client uses OAuth 2.1 with PKCE. Each access token is bound to one resource, and refresh tokens rotate with replay detection.
Service to Google. Each service uses separate Google credentials and the minimum required OAuth scopes. Google refresh tokens are never returned to MCP clients.
Only the state core for the first layer exists today. HTTP endpoints and the second authorization layer are not implemented.
Git
Python 3.14
uv
A Google Cloud project and OAuth client will be required after the Google API integration is implemented. The current version does not use them.
git clone https://github.com/hawkxdev/google-workspace-mcp.git
cd google-workspace-mcp
uv sync --devThe virtual environment does not need to be activated. Run commands through uv run.
uv run --no-sync pytest -q
uv run --no-sync ruff check .
uv run --no-sync ruff format --check .
uv run --no-sync mypy srcThe --no-sync flag is required when checking the installed dependency version. A plain uv run may resynchronize the environment from the lock file.
Path | Purpose |
| downstream OAuth state lifecycle |
| immutable per-service environment configuration |
| five placeholder entry points |
| OAuth core and package entry point regressions |
| package metadata, dependencies, and tool configuration |
| provenance of adapted code |
The project is in early development. Before making a substantial change, open an issue describing the proposed behavior. Changes must not merge the five services into one process, share credentials between services, or introduce an OAuth bypass.
The project adapts the OAuth 2.1 core from jimprosser/obsidian-web-mcp under the MIT License. See NOTICE for details.
The downstream OAuth 2.1 core is based on revision 7e6a52d791a50e3bd533df1060217973ab5be1c8. It includes additional fixes for client and token lifecycles, refresh token rotation, replay detection, and resource canonicalization.
The original project's Obsidian storage and Git synchronization functionality was not copied.
This project uses mcp>=2,<3. The mcp.server.fastmcp package removed in MCP 2.0 is not required; future composition will use mcp.server.mcpserver.
MIT, see LICENSE.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
AI-powered medical document management for cancer patients. Google Drive, Gmail, Calendar via MCP.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hawkxdev/google-workspace-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server