Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

gws-mcp-server

Maintenance mode. This project is stable and receives security fixes. New features aren't planned, but issues and pull requests are still welcome.

Google Workspace for AI agents: Gmail, Calendar, Drive, Sheets, Docs, Slides, Tasks, and Contacts as a curated set of 67 Model Context Protocol tools, built on the official Google Workspace CLI (gws).

npm version License: MIT Node Podcast X


Why?

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 write tool declares all four MCP annotation hints — readOnlyHint, destructiveHint, idempotentHint, openWorldHint — and every read tool declares readOnlyHint and openWorldHint (the MCP spec ignores destructiveHint and idempotentHint when readOnlyHint is true), so clients can reason about side effects, know which writes are safe to retry, and surface clearer consent prompts. This is the permissions leg of trust infrastructure for agents: a deliberately narrow tool surface, side effects declared on every tool, and no freestanding send tool — the only outbound email an agent can trigger is calendar invite/update notifications, opt-in via sendUpdates and off by default.

Related MCP server: Vopak Workspace MCP

Prerequisites

  • Node.js 18+

  • gws CLI installed and authenticated (npm install -g @googleworkspace/cli && gws auth login)

Grant fewer scopes than the default

This server exposes no freestanding send tool — gmail_drafts_create explicitly does not send, and the only outbound email an agent can trigger is calendar invite/update notifications via sendUpdates, which is enum-validated and defaults to none. The token gws auth login mints is broader than that.

gws auth login opens a scope picker listing nine scopes. The default grant is seven: full read-write drive, spreadsheets, gmail.modify (Google documents it as "Read, compose, and send emails"), calendar, documents, presentations, and tasks — the same seven you get running non-interactively as DEFAULT_SCOPES.

The other two rows are Cloud Pub/Sub and Cloud Platform, and neither is part of the default grant — gws auth login --help describes --full as "Request all scopes incl. pubsub + cloud-platform."

Which rows start checked has not been verified against a live picker — the seven above are the documented default grant, not an observation of the TUI. Read the checkboxes before pressing Enter rather than trusting this paragraph.

So the token on disk can send mail and rewrite Drive even though nothing here will. Deselect what you do not need in the picker, or:

gws auth login --readonly    # read-only across services

-s gmail limits the picker to Gmail, per the flag's own help text ("Comma-separated service names to limit scope picker"). It cannot pull in cloud-platform or pubsub, because those two are reachable only through --full. It also replaces any credential you already have rather than adding to it. To add a service to an existing login, use gws-mcp-server auth login.

On Linux there is no keyring, and the encryption key is a file next to the data it encrypts. gws enables the keyring crate's native backends only for macOS and Windows; on every other platform the dependency is declared with no backend feature, so the store falls through to writing .encryption_key into ~/.config/gws/. That file is not a backup of a key held elsewhere — it is the key, and the credential store's own doc comment says it is never deleted. Setting GOOGLE_WORKSPACE_CLI_KEYRING_BACKEND=file changes nothing there because that is already the only path. On macOS and Windows the key file is removed once the OS keyring holds the key. If you run this headless on Linux, treat ~/.config/gws/ as a password file: anyone who can read the directory has the credentials.

Contacts needs a scope outside the default grant

The people_* tools need the contacts scope, which the default gws auth login (and the seven-scope grant described above) does not request.

Add Contacts with gws-mcp-server auth login -s people, not gws auth login -s people. gws's own filtered login replaces the saved credential with only the filtered scopes, so it drops Drive, Gmail, Calendar and everything else you had granted (#68, tracked upstream in googleworkspace/cli#673). This server's auth login does incremental authorization instead:

gws-mcp-server auth login -s people              # keep existing scopes, add contacts
gws-mcp-server auth login -s people --dry-run    # print the gws command first

It reads the scopes the saved credential holds from gws auth status, adds the requested services' scopes, and runs gws auth login --scopes <existing + new>. You consent once in the browser, and afterwards it re-reads gws auth status and exits non-zero if any scope you asked for (old or new) wasn't granted, for example because a box was unticked on Google's consent screen. gws saves whatever the consent screen granted, so an unticked box does remove that scope from the saved credential. Before the browser opens, and again if anything is missing afterwards, the command prints the gws auth login --scopes "..." command that re-requests the complete list. It needs a client configured for gws auth login already, and it exits without changing anything if the credential already covers the services.

Flag

Effect

--services, -s <list>

Services whose scopes to add (required)

--readonly

Add each service's read-only scope (skipped when the read-write scope is already held)

--dry-run

Print the gws auth login command without running it

--replace

The old behaviour: replace the credential with only the requested scopes

--gws-path <path>

gws binary, same as the server flag

gws auth status discovers scopes live (refresh-token exchange plus Google's token-info lookup), so the scopes field can be missing when that fails. When a saved credential exists but its scopes can't be read, auth login refuses rather than guessing; fix the status lookup and retry. If you really mean to start over with only the requested scopes, pass --replace. With no saved credential at all it is a first login and requests just the services you name.

If you prefer to run gws directly, pass the complete list yourself. For a credential that used exactly the default seven scopes described above:

gws auth login --scopes "https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/spreadsheets,https://www.googleapis.com/auth/gmail.modify,https://www.googleapis.com/auth/calendar,https://www.googleapis.com/auth/documents,https://www.googleapis.com/auth/presentations,https://www.googleapis.com/auth/tasks,https://www.googleapis.com/auth/contacts"

The People API must also be enabled on your own GCP project — a one-time step separate from OAuth, since a new scope grant doesn't enable a new API by itself:

gcloud services enable people.googleapis.com --project=<your-project-id>

Without both steps, people_* tools fail: a missing scope surfaces as a 401/403 from Google, and a disabled API surfaces as a distinct 403 naming the API and a console link to enable it.

Quick start

# Install
npm install -g gws-mcp-server

# Or run from source
git clone https://github.com/conorbronsdon/gws-mcp-server.git
cd gws-mcp-server
npm install && npm run build

Configuration

Claude Code (.mcp.json)

{
  "mcpServers": {
    "google-workspace": {
      "command": "npx",
      "args": [
        "gws-mcp-server",
        "--services", "drive,sheets,calendar,docs,slides,gmail,tasks"
      ]
    }
  }
}

Contacts is opt-in because it needs additional authentication and API setup. After completing the Contacts prerequisites, append people to the service list:

"args": ["gws-mcp-server", "--services", "drive,calendar,people"]

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "google-workspace": {
      "command": "npx",
      "args": [
        "gws-mcp-server",
        "--services", "drive,sheets,calendar"
      ]
    }
  }
}

Options

Flag

Description

Default

--services, -s

Comma-separated list of services to expose

Core services; people is opt-in

--gws-path

Path to the gws binary

GWS_BINARY or gws

--read-only

Register only the read-only tools

off

--file-root <dir>

Directory that uploadPath and savePath files must resolve inside

working directory

On Windows, npm's gws.cmd is resolved to its JavaScript entry point and run with Node. --gws-path or GWS_BINARY may also point directly to a JavaScript entry point or .exe.

--read-only

--read-only registers 26 tools instead of the default 61. Every tool that writes to Google is left unregistered, so it never appears in tools/list and there is nothing for an agent to call — including gmail_drafts_create, which is a write even though it never sends. drive_files_download stays, since it reads. Explicitly adding people raises those counts to 29 read-only tools out of 67 total.

gws-mcp-server --read-only
gws-mcp-server --read-only --services drive,calendar   # combines with -s

This constrains the agent, not the credential. The token on disk keeps whatever scopes it was granted, and anything else on the machine can still use it. gws auth login --readonly is what narrows the token; the two are complementary. For an MCP server the agent is the threat model, but that is the limit of the claim.

--file-root

Tools that take uploadPath read a local file and send it to Drive. The path must resolve inside the file root after symlinks are followed, so an agent cannot upload ~/.config/gws/client_secret.json, ~/.config/gcloud credentials or an ~/.ssh key from outside it. A relative uploadPath resolves against the root. Hard-linked files are refused, even when every link is inside the root, since the link count cannot show where the other names are and a hard link can alias a file outside the root.

drive_files_download savePath writes downloaded bytes to a local file, so it follows the same root: the save directory must exist and resolve to the root itself or a directory inside it, which keeps an agent from overwriting gws credentials, shell startup files or ~/.ssh/authorized_keys. An existing in-root file can still be overwritten, unless it is a symlink or a hard link. The path is checked before anything is downloaded and again on the open file before it is written, so a link swapped in between is refused. The save directory is re-checked as well: if it is replaced by a symlink after the first check, the write is refused. A swap in the instant just before the open can leave an empty new file in the other directory, and a refused write can leave an empty new file at the save path, but no byte is written to either. The refused file is not deleted, because after a swap its path may name a different file. An existing file is overwritten in place, so a disk or I/O error during the write (for example a full disk) can leave it empty or partly written, and its old contents are lost. A new file is created exclusively, so on Linux and macOS nothing is created through a symlink. On Windows, which has no O_NOFOLLOW, the open can follow a symlink swapped in after the first check: opening an existing file reaches its target, and creating a new file through a dangling symlink leaves an empty file at the link's target, which may be outside the root. The second check then refuses the write before any byte is written, but it runs after the open rather than in it. The root defaults to the server's working directory (/app in the Docker image). Point it at a dedicated directory rather than your home directory:

gws-mcp-server --file-root ~/gws-uploads

Current gws builds also confine --upload to their own working directory, which is the server's working directory. If you set --file-root somewhere else, start the server from that directory too; the server prints a warning at startup when the root is outside its working directory.

Trimming context cost

Every registered tool rides along in each conversation. The default registry is roughly 46 KB of tools/list payload (~11.8K tokens); opting into people raises the full registry to roughly 52 KB (~13.2K tokens). The two flags above compose, and dropping whole services you don't use is the cheapest context win there is:

gws-mcp-server --services calendar                       # calendar assistant: 6 tools
gws-mcp-server --services drive,docs                     # document work, nothing else
gws-mcp-server --read-only --services drive,docs,sheets  # research setup: reads only

In .mcp.json or claude_desktop_config.json, the same trimming is just editing the args array:

"args": ["gws-mcp-server", "--services", "drive,calendar"]

A service's tool count (headers below) tracks its context cost: dropping drive (24 tools) saves the most, docs (3 tools) the least. There is no per-tool exclude flag today — if service granularity is too coarse for your setup, open an issue describing the split you need.

Available services & tools

drive (24 tools)

  • 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 (an uploadPath replaces the file's content; destructive)

  • 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

  • drive_permissions_list — List all permissions on a file (audit sharing state, e.g. check for public access)

  • drive_permissions_update — Change an existing permission's role (e.g. reader to writer); downgrades remove capabilities. Use the dedicated transfer tools below for ownership changes.

  • drive_permissions_delete — Revoke a permission from a file

  • drive_permissions_transferOwnership — Immediately transfer ownership to another Google Workspace account in the SAME organization, downgrading the current owner to writer; sends a mandatory notification email; not supported for shared drive files

  • drive_permissions_proposeOwnershipTransfer — Propose transferring ownership between personal/consumer accounts; the recipient must separately accept (mandatory email notification), this doesn't transfer it outright

  • drive_comments_list — List comments on a file (works on any Drive file, not just Docs/Sheets/Slides)

  • drive_comments_get — Get a single comment

  • drive_comments_create — Add a comment, optionally anchored to an app-defined region (Workspace editors still show it as unanchored)

  • drive_comments_update — Change a comment's text (author-only)

  • drive_comments_delete — Permanently delete a comment (author-only)

  • drive_replies_list — List replies to a comment

  • drive_replies_get — Get a single reply

  • drive_replies_create — Reply to a comment, or resolve/reopen it via the action field

  • drive_replies_update — Change a reply's text (author-only)

  • drive_replies_delete — Permanently delete a reply (author-only)

sheets (5 tools)

  • sheets_get — Get spreadsheet metadata

  • sheets_values_get — Read cell values

  • sheets_values_update — Write cell values (overwrites the range; destructive)

  • sheets_values_append — Append rows

  • sheets_batchUpdate — Apply updates to a spreadsheet (conditional formatting, cell/border formatting, adding sheets, and more; delete requests are permanent)

calendar (6 tools)

  • calendar_events_list — List events

  • calendar_events_get — Get event details

  • calendar_events_insert — Create events, optionally with attendees. sendUpdates controls invitation email (default none — no email, though the event may still appear on attendees' calendars depending on their settings)

  • calendar_events_update — Update events (only supplied fields change — except attendees, which replaces the whole list; omitted attendees are uninvited, so the tool is marked destructive even for calls without attendees). Same sendUpdates support as insert

  • calendar_events_delete — Delete events

  • calendar_freebusy_query — Query free/busy information for one or more calendars over a time range

docs (3 tools)

  • docs_get — Get document content

  • docs_create — Create documents

  • docs_batchUpdate — Apply document updates

slides (5 tools)

  • slides_get — Get a presentation's slides, layouts, masters, and page elements

  • slides_create — Create a blank presentation

  • slides_batchUpdate — Apply updates (insert/update/delete slides, text, shapes, tables, etc)

  • slides_pages_get — Get a single page (slide, layout, or master)

  • slides_pages_getThumbnail — Get a thumbnail image URL for a page

gmail (6 tools)

  • gmail_messages_list — Search messages

  • gmail_messages_get — Read a message

  • gmail_threads_list — Search threads

  • gmail_threads_get — Read a full thread

  • gmail_threads_modify — Add/remove labels on a thread (archive, mark read, star)

  • gmail_drafts_create — Create a draft (plain text and/or HTML, with reply threading via threadId). Drafts are never auto-sent

tasks (12 tools)

  • tasks_tasklists_list — List task lists

  • tasks_tasklists_get — Get a task list

  • tasks_tasklists_insert — Create a task list

  • tasks_tasklists_update — Update a task list (only supplied fields change)

  • tasks_tasklists_delete — Delete a task list

  • tasks_tasks_list — List tasks (filters: completed/hidden/due dates)

  • tasks_tasks_get — Get a task

  • tasks_tasks_insert — Create a task (optionally nested or positioned)

  • tasks_tasks_update — Update a task (only supplied fields change; common use: mark complete)

  • tasks_tasks_move — Move a task within/across lists or reorder

  • tasks_tasks_delete — Delete a task

  • tasks_tasks_clear — Hide all completed tasks in a list

people (6 tools)

Needs the contacts scope and an enabled People API — see Contacts needs a scope outside the default grant.

  • people_people_get — Get a contact by resource name (or people/me for the authenticated user)

  • people_people_searchContacts — Search contacts by name, email, phone, or organization

  • people_people_createContact — Create a new contact

  • people_people_updateContact — Update a contact (requires the current etag in the request body)

  • people_people_deleteContact — Permanently delete a contact

  • people_connections_list — List the authenticated user's contacts

Update semantics: the *_update tools (calendar events, tasks, task lists) use the Google API's patch verb — they merge the fields you supply and leave the rest untouched. To clear an existing value, pass it explicitly (e.g. an empty string) rather than omitting it.

Total: 67 supported tools; 61 enabled by default (vs 200-400 in the old implementation)

Adding new tools

Edit src/services.ts to add tool definitions. Each tool maps directly to a gws CLI command:

{
  name: "drive_files_list",           // MCP tool name
  description: "List files in Drive", // Shown to AI
  command: ["drive", "files", "list"],// gws CLI args
  params: [                           // Maps to --params JSON
    { name: "q", description: "Search query", type: "string", required: false },
  ],
  bodyParams: [                       // Maps to --json body
    { name: "name", description: "File name", type: "string", required: true },
  ],
}

Typed errors

Tool call failures are mapped to a typed error hierarchy (src/errors.ts): AuthenticationError (401/403), RateLimitError (429), ValidationError (400), NotFoundError (404, with a shared-drive access hint for drive commands), and ServerError (5xx), all extending a base GwsError. Unlike an HTTP API client, this server has no response object to read a status code from — it spawns the gws CLI as a subprocess and only sees plain text (stdout/stderr, or a rejected promise's .message). mapGwsErrorToTyped() recovers a status-like code from that text, handling both a raw JSON error body (Google's own {"error":{"code":...,"message":...}} shape) and plain text containing an HTTP-status-like token (e.g. "Error 404: ..."). If neither pattern is found, the original message passes through unchanged rather than forcing an invented status onto it.

Architecture

MCP Client (Claude) ←→ stdio ←→ gws-mcp-server ←→ gws CLI ←→ Google APIs

The server is a thin wrapper: it translates MCP tool calls into gws CLI invocations, passes --params and --json as appropriate, and returns the JSON output. Authentication stays in the gws CLI — this server never sees or stores your Google credentials.

Development

git clone https://github.com/conorbronsdon/gws-mcp-server.git
cd gws-mcp-server
npm ci
npm run lint    # type-check
npm run build
npm test        # vitest, mocks the executor layer — no real gws calls

Contributing

Issues and pull requests are welcome. Keep the curated contract: a focused set of narrowly scoped tools, not a 1:1 mirror of every Google API surface. Before writing a PR for a new service, open an issue describing the use case, required scopes and side effects; docs/scope-policy.md explains what belongs here and what fits better as a companion server. Improvements to existing tools are welcome directly. See SECURITY.md for how to report vulnerabilities.

Companion servers

Services outside the curated set can ship as separate MCP servers that run alongside this one, each with its own scope grant. Community companion servers that declare side effects on every tool and add no freestanding send action will be listed here.

Other options

This server is deliberately narrow: a curated tool surface, side effects declared on every tool, no freestanding send tool. That is the right trade for some workflows and the wrong one for others. The real alternatives:

You want

Use

Every Workspace API, self-hosted, with tiers and multi-user OAuth

taylorwilsdon/google_workspace_mcp — 120+ tools across 12 services, MIT, --tool-tier core|extended|complete

Google's own servers, hosted by Google

Google Workspace remote MCP servers — 8 endpoints, 42 tools. Developer Preview: requires an application, a Workspace account (not personal Gmail), and a supported client plan

No MCP at all — CLI plus agent skills

googleworkspace/cli — 100+ Agent Skills on the same gws auth login this server uses

Worth saying plainly: Google's official Gmail MCP server is also draft-only, with no send tool — the curated-surface argument is no longer contrarian. What this server still does that those don't: Google Tasks (Google's official lineup has no Tasks server), all four MCP annotation hints on every write tool (reads declare readOnlyHint and openWorldHint), a local stdio server with no preview application or plan gating, and --read-only as a single flag.

The analytics siblings

Data

Server

Google Workspace

this repo

Search Console

gsc-mcp — same curated approach, including derived views like gsc_striking_distance

YouTube Analytics

yt-analytics-mcp — owner-side channel, video, and playlist metrics; read-only, nine tools

Google Analytics 4

googleanalytics/google-analytics-mcp — Google's own, read-only

BigQuery

googleapis/mcp-toolbox — Google's own

These are separate credential families, not one login: Workspace authenticates with gws auth login, Search Console with a webmasters OAuth credential, YouTube Analytics with a yt-analytics.readonly OAuth credential, GA4 with Application Default Credentials scoped analytics.readonly. Nothing here shares a token with anything else.

About

Built and maintained by Conor Bronsdon. I host the Chain of Thought podcast, which covers AI infrastructure, developer tools, and how practitioners actually use this stuff. I built this to give the agent workflows that run the show safe, curated access to Gmail, Calendar, Drive, Sheets, Docs, Slides, Tasks, and Contacts.

Companion tools:

  • Transistor MCP: Transistor.fm's official MCP server. Episodes, publishing, and analytics.

  • substack-mcp: read posts and manage drafts on Substack, safe for agent workflows.

  • podcastindex-mcp: the Podcast Index MCP server, search by person or topic, trending shows, feed health.

  • op3-mcp: podcast analytics through OP3. Downloads, geography, apps. Read-only.

  • ai-tools-for-creators: a curated list of AI skills and MCP servers for people who ship ideas for a living.

More at chainofthought.show and on X.


Disclaimer

This is an independent personal project, not affiliated with, sponsored by, or endorsed by any company. All views expressed are my own.

License

MIT

Available Tools

61 tools
calendar_events_deleteC
DestructiveIdempotent

Delete a calendar event.

Inputs: eventId (required), calendarId (required).

calendar_events_getB
Read-only

Get a single calendar event by ID.

Inputs: eventId (required), calendarId (required).

calendar_events_insertC

Create a new calendar event.

Inputs: end (required), start (required), summary (required), calendarId (required), +4 more.

calendar_events_listC
Read-only

List events from a calendar.

Inputs: calendarId (required), q, orderBy, timeMax, +3 more.

calendar_events_updateA
Destructive

Update an existing calendar event with patch semantics (only supplied fields change). attendees replaces the whole list and anyone omitted is uninvited. Because it can do that, the whole tool is marked destructive, including calls without attendees.

Inputs: eventId (required), calendarId (required), end, start, +4 more.

calendar_freebusy_queryC
Read-only

Query free/busy information for one or more calendars over a time range.

Inputs: items (required), timeMax (required), timeMin (required), timeZone.

docs_batchUpdateB
Destructive

Apply updates to a Google Doc (insert, format, replace, or permanently delete content).

Inputs: requests (required), documentId (required).

docs_createB

Create a new empty Google Doc.

Inputs: title (required).

docs_getB
Read-only

Get a Google Doc's content and metadata.

Inputs: documentId (required).

drive_comments_createA

Add a comment to a file. Set anchor to bind it to an app-defined region — Drive stores this as an opaque JSON string you define yourself, and does not validate or interpret it. Google Workspace editor apps (Docs/Sheets/Slides) still display comments created this way as unanchored; use the Docs/Sheets/Slides APIs directly if visual anchoring in those editors matters.

Inputs: fields (required), fileId (required), content (required), anchor.

drive_comments_deleteA
DestructiveIdempotent

Permanently delete a comment. Only the comment's own author can delete it — the API rejects the request otherwise.

Inputs: fileId (required), commentId (required).

drive_comments_getC
Read-only

Get a single comment on a file.

Inputs: fields (required), fileId (required), commentId (required), includeDeleted.

drive_comments_listC
Read-only

List comments on a file.

Inputs: fields (required), fileId (required), pageSize, pageToken, +2 more.

drive_comments_updateA
DestructiveIdempotent

Change the text of an existing comment. This overwrites the comment's content; the previous text is not retained. Only the comment's own author can update it — the API rejects the request otherwise. The resolved state can't be changed here: see drive_replies_create's action field.

Inputs: fields (required), fileId (required), content (required), commentId (required).

drive_files_copyB

Copy a file. Useful for converting formats (e.g. markdown to Google Doc).

Inputs: name (required), fileId (required), fields, parents, +1 more.

drive_files_createB

Create a new file in Google Drive. Use with bodyParams for metadata and optionally upload a local file.

Inputs: name (required), fields, parents, mimeType, +1 more.

drive_files_deleteB
DestructiveIdempotent

Permanently delete a file.

Inputs: fileId (required).

drive_files_downloadA
Read-only

Download a file's content from Google Drive. Returns the text content for text files, or a base64-encoded string for binary files. For Google Docs/Sheets/Slides, exports to a readable format (plain text by default).

Inputs: fileId (required), savePath, exportMimeType.

drive_files_exportA
Read-only

Export a Google Workspace file (Doc, Sheet, Slide) to a specific format. Returns JSON with export metadata. Use drive_files_download for automatic export with content returned inline.

Inputs: fileId (required), mimeType (required).

drive_files_getA
Read-only

Get a file's metadata by ID. Shared drive files are supported automatically.

Inputs: fileId (required), fields.

drive_files_listB
Read-only

List files in Google Drive. Supports search queries via the 'q' parameter. Shared drive files are included automatically.

Inputs: q, fields, orderBy, pageSize.

drive_files_updateA
DestructiveIdempotent

Update a file's metadata or content. An uploadPath replaces the file's content and no copy of the old content is kept. Because it can do that, the whole tool is marked destructive, including calls without uploadPath.

Inputs: fileId (required), name, fields, mimeType, +1 more.

drive_permissions_createC

Share a file by creating a permission.

Inputs: role (required), type (required), fileId (required), emailAddress.

drive_permissions_deleteA
DestructiveIdempotent

Revoke a permission from a file, removing that user's/group's/domain's access. Per the Drive API: concurrent permissions operations on the same file aren't supported, only the last update is applied.

Inputs: fileId (required), permissionId (required).

drive_permissions_listA
Read-only

List all permissions on a file. Use to audit sharing state — e.g. a permission with type "anyone" means the file is publicly accessible; there is no separate is-public field. Pass fields (e.g. "permissions(id,type,role,emailAddress,domain)") to identify grantees — the default response omits emailAddress/domain.

Inputs: fileId (required), fields, pageSize, pageToken.

drive_permissions_proposeOwnershipTransferA

Propose transferring ownership of a file between personal/consumer Google accounts (use drive_permissions_transferOwnership instead for a same-organization Workspace transfer, which completes immediately). Google Workspace ownership cannot be transferred to an account outside the organization. This does NOT transfer ownership by itself: it sets role=writer + pendingOwner=true, and the prospective owner must separately accept by setting role=owner + transferOwnership=true on their own permission, under their own credentials. Google sends the recipient a notification email that cannot be disabled; nothing changes for the current owner unless and until they accept. Only individual users can be proposed — not groups, domains, or service accounts (service accounts have no Drive storage quota and the transfer will fail). Ownership transfers are not supported for files in shared drives.

Inputs: fileId (required), emailAddress (required), fields.

drive_permissions_transferOwnershipA
Destructive

Immediately transfer ownership of a file to another Google Workspace account in the SAME organization. The current owner is downgraded to writer as soon as this call succeeds — there is no separate acceptance step — and Google sends the new owner a notification email that cannot be disabled. Only works for files in "My Drive"; not supported for files in a shared drive, since the organization owns those, not an individual. For a transfer between personal/consumer Google accounts, use drive_permissions_proposeOwnershipTransfer instead, which requires the recipient's separate acceptance and does not transfer ownership immediately. Google Workspace ownership cannot be transferred to an account outside the organization.

Inputs: fileId (required), emailAddress (required), fields, moveToNewOwnersRoot.

drive_permissions_updateA
DestructiveIdempotent

Change an existing permission's role on a file (e.g. reader to writer). Can remove capabilities by downgrading a role. Ownership transfers are not supported. Per the Drive API: concurrent permissions operations on the same file aren't supported, only the last update is applied.

Inputs: role (required), fileId (required), permissionId (required), fields.

drive_replies_createA

Add a reply to a comment, or resolve/reopen it — a comment can only be resolved or reopened by posting a reply with action set. content is required unless action is set; combine both to leave closing/reopening text. Setting action changes the parent comment's resolved field, but resolving is advisory only: the API keeps accepting further replies and doesn't hide anything itself, it's on the client to act on resolved being true (e.g. hide or dim the thread).

Inputs: fileId (required), commentId (required), action, fields, +1 more.

drive_replies_deleteA
DestructiveIdempotent

Permanently delete a reply. Only the reply's own author can delete it — the API rejects the request otherwise.

Inputs: fileId (required), replyId (required), commentId (required).

drive_replies_getB
Read-only

Get a single reply to a comment.

Inputs: fileId (required), replyId (required), commentId (required), fields, +1 more.

drive_replies_listC
Read-only

List replies to a comment.

Inputs: fileId (required), commentId (required), fields, pageSize, +2 more.

drive_replies_updateA
DestructiveIdempotent

Change the text of an existing reply. This overwrites the reply's content; the previous text is not retained. Only the reply's own author can update it — the API rejects the request otherwise. Does not support changing action — use drive_replies_create to resolve/reopen.

Inputs: fileId (required), content (required), replyId (required), commentId (required), +1 more.

gmail_drafts_createA

Create a Gmail draft. Pass threadId to attach the draft to an existing conversation (it will appear as a reply within that thread). The draft is NOT sent — open Gmail to review and send.

Inputs: to (required), cc, bcc, body, +5 more.

gmail_messages_getC
Read-only

Get a single Gmail message by ID.

Inputs: id (required), userId (required), format.

gmail_messages_listC
Read-only

List Gmail messages matching a query.

Inputs: userId (required), q, labelIds, maxResults.

gmail_threads_getA
Read-only

Get a full Gmail thread by ID (all messages in the conversation).

Inputs: id (required), userId (required), format.

gmail_threads_listC
Read-only

List Gmail threads matching a query.

Inputs: userId (required), q, maxResults.

gmail_threads_modifyA
Idempotent

Modify a Gmail thread: add/remove labels. To archive, remove INBOX. To mark read, remove UNREAD. To star, add STARRED.

Inputs: id (required), userId (required), addLabelIds, removeLabelIds.

sheets_batchUpdateA
Destructive

Apply updates to a spreadsheet (conditional formatting, cell/border formatting, adding sheets, and more). Can also permanently delete content — e.g. removing a sheet or a conditional formatting rule — with no undo via the API.

Inputs: requests (required), spreadsheetId (required).

sheets_getC
Read-only

Get spreadsheet metadata.

Inputs: spreadsheetId (required), includeGridData.

sheets_values_appendA

Append values after the last row of a spreadsheet range.

Inputs: range (required), values (required), spreadsheetId (required), valueInputOption (required).

sheets_values_getC
Read-only

Read values from a spreadsheet range.

Inputs: range (required), spreadsheetId (required), majorDimension, valueRenderOption.

sheets_values_updateA
DestructiveIdempotent

Write values to a spreadsheet range. Overwrites the values already in the range; the previous values are not kept, so this tool is marked destructive.

Inputs: range (required), values (required), spreadsheetId (required), valueInputOption (required).

slides_batchUpdateA
Destructive

Apply updates to a presentation (insert/update/delete slides, text, shapes, tables, etc). Delete requests in a batch are permanent — the API has no undo.

Inputs: requests (required), presentationId (required).

slides_createB

Create a new blank presentation.

Inputs: title (required).

slides_getA
Read-only

Get a presentation's slides, layouts, masters, and page elements.

Inputs: presentationId (required).

slides_pages_getB
Read-only

Get a single page (slide, layout, or master) from a presentation.

Inputs: pageObjectId (required), presentationId (required).

slides_pages_getThumbnailB
Read-only

Get a thumbnail image URL for a page (slide, layout, or master).

Inputs: pageObjectId (required), presentationId (required), thumbnailProperties.mimeType, thumbnailProperties.thumbnailSize.

tasks_tasklists_deleteA
DestructiveIdempotent

Delete a task list. If it contains assigned tasks, the originals (in Docs/Chat Spaces) are also removed.

Inputs: tasklist (required).

tasks_tasklists_getC
Read-only

Get a task list by ID.

Inputs: tasklist (required).

tasks_tasklists_insertB

Create a new task list.

Inputs: title (required).

tasks_tasklists_listB
Read-only

List the authenticated user's task lists.

Inputs: pageToken, maxResults.

tasks_tasklists_updateB
Idempotent

Update a task list (only supplied fields change).

Inputs: tasklist (required), title.

tasks_tasks_clearA
DestructiveIdempotent

Hide all completed tasks in a list. Cleared tasks are not deleted but stop appearing in default list responses.

Inputs: tasklist (required).

tasks_tasks_deleteA
DestructiveIdempotent

Delete a task. If assigned from Docs/Chat Spaces, the original is also removed.

Inputs: task (required), tasklist (required).

tasks_tasks_getB
Read-only

Get a task by ID.

Inputs: task (required), tasklist (required).

tasks_tasks_insertB

Create a new task. Use parent to nest as a subtask, previous to position after a sibling.

Inputs: title (required), tasklist (required), due, notes, +3 more.

tasks_tasks_listA
Read-only

List tasks in a task list. Excludes hidden and assigned tasks by default; set showHidden/showAssigned to include them.

Inputs: tasklist (required), dueMax, dueMin, pageToken, +8 more.

tasks_tasks_moveA
Idempotent

Move a task within its list or to another list. Use parent/previous to set position; destinationTasklist to change list.

Inputs: task (required), tasklist (required), parent, previous, +1 more.

tasks_tasks_updateA
Idempotent

Update a task (only supplied fields change). Common use: complete a task by setting status to "completed".

Inputs: task (required), tasklist (required), due, notes, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 61 tools

    Disambiguation4/5

    Most tools are cleanly scoped to a resource+action within a clearly named product namespace (drive_files_*, sheets_values_*, calendar_events_*, tasks_tasks_*), so an agent can pick correctly in the common case. A few pairs need careful reading: drive_files_export vs drive_files_download, drive_files_update vs drive_files_copy, and the two ownership-transfer tools overlap conceptually (mitigated by very explicit descriptions).

    Naming Consistency3/5

    The dominant pattern is product_resource_action in snake_case, but verbs are mixed (create vs insert: drive_files_create, docs_create, slides_create but tasks_tasks_insert, calendar_events_insert) and camelCase appears in several names (sheets_batchUpdate, slides_batchUpdate, docs_batchUpdate, slides_pages_getThumbnail, drive_permissions_transferOwnership). It remains readable and predictable per-product, but not a single consistent convention.

    Tool Count3/5

    61 tools is far above the typical well-scoped range and makes the surface heavy to navigate, though the count is explained by bundling seven Google products (Drive, Docs, Sheets, Slides, Calendar, Gmail, Tasks). Each product's subset is reasonably sized, so the total is borderline rather than gratuitous.

    Completeness3/5

    Drive, Tasks, Calendar, and Slides have near-complete lifecycles, but Gmail is a notable hole: there is no send-message or send-draft tool, and label management is only partially exposed via gmail_threads_modify. Docs also lacks delete/move-style operations, forcing agents to route through Drive, and there is no tool to enumerate calendars or spreadsheets beyond Drive file listing.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers