gworkspace-mcp
Provides tools for composing and sending emails through Gmail's API, enabling email automation directly from conversation interfaces.
Enables management of Google Calendar events and scheduling through the Calendar API, though specific capabilities beyond scope listing aren't detailed.
Requires a Google Cloud project with specific APIs enabled for authentication and authorization to access Google Workspace services.
Provides tools for reading and editing Google Docs documents programmatically through the Docs API.
Offers tools for listing, searching, moving, and managing files and folders in Google Drive through the Drive API.
Provides comprehensive spreadsheet manipulation tools including reading/writing ranges, batch updates, formatting, protection, formulas, and dashboard creation through the Sheets API.
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., "@gworkspace-mcpadd a new sheet named 'Q4 Results' to my budget spreadsheet"
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.
gworkspace-mcp
Model Context Protocol server for Google Workspace automation: Google Sheets, Apps Script, Drive, Docs, Gmail, and triggers. Built with FastMCP.
Designed to be used from Claude Code (or any MCP-compatible client) so you can edit Apps Script projects, manipulate spreadsheets, send emails and manage Drive files directly from a conversation.
Features
Apps Script (9 tools) — list, read, update, create, deploy and run Apps Script projects. Granular file edits so you don't have to rewrite entire scripts.
Sheets (10 tools) — read/write ranges, batch updates, formatting, protection, formulas, dashboards.
Drive (4 tools) — list, search, move and manage files.
Docs (1 tool) — read/edit Google Docs.
Gmail (3 tools) — compose and send email.
Triggers (3 tools) — manage Apps Script time-based and event triggers.
Connect (1 tool) — bind a local Apps Script project to a spreadsheet.
Requirements
Python 3.10+
A Google Cloud project with the following APIs enabled:
Google Sheets API
Google Drive API
Apps Script API
Google Docs API
Gmail API
Google Calendar API
OAuth 2.0 Desktop credentials (
client_secret.json)
Installation
git clone https://github.com/LeooNic/gworkspace-mcp.git
cd gworkspace-mcp
pip install -e .Or with uv:
uv pip install -e .Google Cloud setup
Go to console.cloud.google.com and create a project.
Enable the APIs listed above under APIs & Services → Library.
Go to APIs & Services → OAuth consent screen, configure it as External, and add your Google account as a test user.
Go to APIs & Services → Credentials → Create Credentials → OAuth client ID, choose Desktop app, and download the JSON.
Make the credentials available to the server in one of these ways:
Place the JSON at
~/.secrets/gworkspace-mcp/client_secret.json, orSet
GOOGLE_CLIENT_SECRET_PATH=/full/path/to/client_secret.json, orSet
GOOGLE_OAUTH_CLIENT_IDandGOOGLE_OAUTH_CLIENT_SECRETas env vars.
The first time a tool runs, a browser window will open for OAuth consent. The resulting token is stored at ~/.secrets/gworkspace-mcp/token.json and refreshed automatically.
Register with Claude Code
Add this to your Claude Code settings.json (or ~/.claude.json):
{
"mcpServers": {
"gworkspace": {
"command": "gworkspace-mcp"
}
}
}If gworkspace-mcp is not on your PATH, use the absolute path to the executable created by pip install -e . (on Windows, typically C:\Users\<you>\AppData\Local\Programs\Python\Python3XX\Scripts\gworkspace-mcp.exe).
Alternative invocation without installing the entry point:
{
"mcpServers": {
"gworkspace": {
"command": "python",
"args": ["-m", "gworkspace_mcp.server"]
}
}
}OAuth scopes
The server requests the following scopes:
spreadsheets,drive,documents,calendarscript.projects,script.deployments,script.processes,script.metricsgmail.send,gmail.composeuserinfo.email,userinfo.profile
Security notes
Your
client_secret.jsonandtoken.jsonare personal — never commit them. The repo.gitignorealready excludes them.Tokens live under
~/.secrets/gworkspace-mcp/.The server runs locally; it does not expose any network endpoint.
License
MIT — see LICENSE.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LeooNic/gworkspace-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server