Expose Workspace APIs dynamically
The CLI reads Discovery Service documents at runtime instead of shipping a fixed command list.
Documentation ↗MCP server / productivity/knowledge / source-linked
Google Workspace CLI MCP
This record should be read as an agent-ready Workspace CLI rather than a current MCP server. It generates command surfaces from Google's Discovery Service, returns structured JSON and ships skills, but the upstream changelog records removal of its `mcp` command in 0.8.0.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Google Workspace CLI (`gws`) is a community GoogleWorkspace GitHub project, not an officially supported Google product; current releases are CLI + agent skills, not MCP server mode.
Implementation source ↗
Google Workspace CLI (`gws`) is a community GoogleWorkspace GitHub project, not an officially supported Google product; current releases are CLI + agent skills, not MCP server mode.
Implementation source ↗
This record should be read as an agent-ready Workspace CLI rather than a current MCP server. It generates command surfaces from Google's Discovery Service, returns structured JSON and ships skills, but the upstream changelog records removal of its `mcp` command in 0.8.0.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- stdio CLI (MCP subcommand removed)
- Authentication
- Google OAuth via gws auth setup/login; credentials can be exported for CI
Install the binary or npm package, then run `gws auth setup`, `gws auth login` and a service command such as `gws drive files list`. Do not copy old `gws mcp` instructions without pinning a historical release.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
npm install -g @googleworkspace/cli && gws auth setup && gws auth loginWhat it actually exposes.
Concrete capabilities with maintainer sources.
Return agent-friendly JSON
Commands support structured JSON, pagination and schema introspection, which can be composed by an agent or shell workflow.
Documentation ↗Install Workspace skills
The repository ships skills for services such as Drive and Gmail and documents installation via `npx skills add`.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
MCP server ignores GOOGLE_WORKSPACE_CLI_ACCOUNT env var
用户在 Linux、Claude Code 和 gws 0.6.0 中同时配置工作账号与个人账号。直接 CLI 调用能按 GOOGLE_WORKSPACE_CLI_ACCOUNT 切换，但 stdio MCP 忽略该变量，两套服务器都使用默认账号。这个差异会造成跨账号数据误读风险；后续关联修复已记录在项目 changelog。
“Both MCP server instances use the default account; the env var is ignored in MCP mode.”Open community source ↗
MCP full-mode tool schemas include body/upload on methods that don't support them
在 full tool mode 中，所有生成的工具都暴露 body 与 upload，即使底层方法不接受请求体或上传。报告者复现 Gmail GET 请求被模型填入空 body 后返回 400，并指出 compact mode 也会转发空对象。该问题体现了工具 schema 设计如何直接影响代理可靠性。
“LLM clients frequently send body: {}, causing Google APIs to return HTTP 400.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed workflow: produce a Drive inventory
Suggested evaluation, not an observed test result.
- Authenticate only the Workspace services the agent needs.
- Run a paginated Drive listing and preserve the structured JSON output.
- Ask the agent to classify files, then review any write command before execution.
What to inspect: A reproducible CLI inventory without claiming MCP compatibility. No command was run for this record.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
The upstream changelog explicitly records removal of the `mcp` command; this page is not evidence of an active Google Workspace MCP endpoint.
Boundary reference ↗The repository states that it is not an officially supported Google product and is under active development with possible breaking changes.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A reproducible CLI inventory without claiming MCP compatibility. No command was run for this record.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Google Drive MCP | Editorial choice: you specifically need the archived local Drive MCP shape for a legacy client. | Archived and incomplete for Shared Drives. Documentation ↗ |
| Microsoft 365 MCP | Editorial choice: enterprise data lives in Microsoft 365 and Copilot extensibility is the target. | A framework for connecting a remote MCP server, not a Workspace API CLI. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Can I configure `gws mcp` today?
The current changelog records the mcp command as removed. Use the CLI and skills documented by the current README, or choose a separately maintained MCP server.
Documentation ↗
Is this made by Google?
The repository explicitly says it is not an officially supported Google product.
Documentation ↗
Source trail.
Maintainer documentation used in this record.