gworkspace-mcp
An MCP server for automating Google Workspace applications including Sheets, Apps Script, Drive, Docs, and Gmail. It enables users to manipulate spreadsheets, edit scripts, manage files, and send emails directly from conversational AI interfaces.
Ask AI about gworkspace-mcp
Powered by Claude Β· Grounded in docs
I know everything about gworkspace-mcp. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
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, or - Set
GOOGLE_CLIENT_SECRET_PATH=/full/path/to/client_secret.json, or - Set
GOOGLE_OAUTH_CLIENT_IDandGOOGLE_OAUTH_CLIENT_SECRETas env vars.
- Place the JSON at
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.
