Google Workspace as 41 curated MCP tools: Gmail, Calendar, Drive, Sheets, Docs, and Tasks.
Google Workspace MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Google Workspace as 41 curated MCP tools: Gmail, Calendar, Drive, Sheets, Docs, and Tasks.
The gws CLI had a built-in MCP server that was removed in v0.8.0 because it exposed 200-400 tools — causing context window bloat in MCP clients. This server takes a curated approach: you choose which Google services to expose, and only a focused set of high-value, narrowly scoped operations are registered as tools. Every tool declares all four MCP annotation hints — readOnlyHint, destructiveHint, idempotentHint, openWorldHint — so clients can reason about side effects, know which writes are safe to retry, and surface clearer consent prompts.
Once Google Workspace is connected, these are the calls the assistant has available:
drive_files_list — Search and list filesdrive_files_get — Get file metadatadrive_files_create — Create files (with optional upload)drive_files_copy — Copy files (useful for format conversion)drive_files_update — Update file metadata/contentdrive_files_delete — Delete filesdrive_files_export — Export Google Workspace files (Doc, Sheet, Slide) to other formatsdrive_files_download — Download file content (text inline, binary as base64 or saved to a path; Google-native files are exported to a readable format)drive_permissions_create — Share filessheets_get — Get spreadsheet metadatasheets_values_get — Read cell valuessheets_values_update — Write cell values@googleworkspace/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
gws CLI installed and authenticated (npm install -g @googleworkspace/cli && gws auth login)Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google Workspace's toolset — drive_files_list, drive_files_get, drive_files_create and 11 more — is a fair guide to whether it matches your workflow. It is maintained by conorbronsdon; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| drive_files_list | Search and list files |
| drive_files_get | Get file metadata |
| drive_files_create | Create files (with optional upload) |
| drive_files_copy | Copy files (useful for format conversion) |
| drive_files_update | Update file metadata/content |
| drive_files_delete | Delete files |
| drive_files_export | Export Google Workspace files (Doc, Sheet, Slide) to other formats |
| drive_files_download | Download file content (text inline, binary as base64 or saved to a path; Google-native files are exported to a readable format) |
| drive_permissions_create | Share files |
| sheets_get | Get spreadsheet metadata |
| sheets_values_get | Read cell values |
| sheets_values_update | Write cell values |
| sheets_values_append | Append rows |
| calendar_events_list | List events |
{
"mcpServers": {
"gws": {
"command": "npx",
"args": ["-y", "@googleworkspace/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.