google_workspace_mcp
Control Gmail, Google Calendar, Docs, Sheets, Slides, Chat, Forms, Tasks, Search & Drive with AI - Comprehensive Google Workspace MCP Server & CLI Tool
Runs with mockssource: GitHubhomepagePythonMITcommit ed70fb906823
Python, MIT licensed. The project labels itself: ai, chatgpt, claude, claude code, claude desktop, gmail, google calendar and google chat.
google_workspace_mcp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
workspace-mcp 1.29.0 installs, builds, launches in both stdio and streamable-http modes, serves a working MCP endpoint with 43 registered tools, passes 2660+ tests with mock Google API credentials, and both CLI entry points (workspace-mcp and workspace-cli) respond to --help
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 72 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- 25 tests in test_contacts_integration.py fail when run after other test files due to shared module-level state (pass 242/242 in isolation)5 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- .venv/bin/python -m pytest tests/core tests/auth tests/gcalendar tests/gmail tests/gdocs tests/gsheets tests/gdrive tests/gcontacts tests/gchat tests/gforms tests/gappsscript tests/test_scopes.py tests/test_main_permissions_tier.py tests/test_permissions.py tests/test_log_hygiene.py tests/test_cwe77_ruff_workflow.py tests/test_slides_tools.py --tb=short -q returned 2660 passed, 25 failed (ordering-dependent); curl POST /mcp with MCP handshake returned 43 tools; GET /health returned 200 OK
- Model tokens used
- 118,002
- Exact commit tested
- ed70fb906823
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
| `gcalendar/` | 270 passed | 1.3s | | `gmail/` | 347 passed | 11.5s | | `gdocs/` | 477 passed | 1.5s | | `gsheets/` | 169 passed | 1.2s | | `gdrive/` | 265 passed | 12.4s | | `gcontacts/` | 242 passed | 1.1s | | `gchat/` | 70 passed | 2.1s | | `gforms/` | 11 passed | 0.9s | | `gappsscript/` | 101 passed | 2.2s | | root-level test files | 88 passed | 2.4s | | **Total** | **2660+** | | When all tests run together in a single session, 25 tests in `tests/gcontacts/test_contacts_integra…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 2 minutes, faster than the median of the 72 comparable projects Argusic has measured.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 73 ai projects Argusic has installed and timed, google_workspace_mcp was the 14th fastest to reach a running state, and 53 of 73 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 72.00 | 0.12 |
Topics (from GitHub)
aichatgptclaudeclaude-codeclaude-desktopgmailgoogle-calendargoogle-chatgoogle-docsgoogle-drivegoogle-formsgoogle-sheetsgoogle-tasksgoogle-workspacegsuitellmllm-toolsmcpmcp-servermodel-context-protocol-server
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/google-workspace-mcp)Questions
- Does google_workspace_mcp run?
- google_workspace_mcp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test google_workspace_mcp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed70fb906823. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test google_workspace_mcp?
- The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does google_workspace_mcp take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does google_workspace_mcp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing google_workspace_mcp?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- How does google_workspace_mcp compare with the alternatives?
- Of the 73 ai projects Argusic has installed and timed, google_workspace_mcp was the 14th fastest to reach a running state, and 53 of 73 reached one at all.
- Where is the evidence for google_workspace_mcp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.