cerase-google-workspace-mcp

A Google Workspace MCP server for Drive, Docs, Sheets, Slides, Calendar and Forms. It is a fork of piotr-agier/google-drive-mcp at release 2.13.0 (@piotr-agier/google-drive-mcp, commit 9509fb8). It serves 142 tools, each described in the tool reference.

Every upstream tool keeps its name, its arguments and its behaviour. The server reads the same credential files and variables as upstream (~/.config/google-drive-mcp/tokens.json, ~/.config/google-drive-mcp/gcp-oauth.keys.json, GOOGLE_DRIVE_OAUTH_CREDENTIALS), so an account already connected to upstream works without being connected again.

What the fork changes

• Suggested edits. suggestInsertText, suggestReplaceText and suggestDeleteText send documents.batchUpdate with writeControl.writeMode = SUGGEST, which the tools set themselves and which no argument can change. The document's visible text stays as it was until its owner accepts each suggestion in Docs. A call answers success only when Google created a suggestion for every request, and names the suggestion ids. Indexes are computed on the document read with suggestionsViewMode = SUGGESTIONS_INLINE, where existing suggestions occupy positions.

• Anchored comments. commentOnText and replyToDocComment comment through the Docs API's insertComment and addCommentReply, so a comment is anchored to the text it is about; a comment made through the Drive API shows unanchored in Docs. listDocCommentsAndSuggestions lists every comment and suggestion thread with its status. No tool accepts or rejects a suggestion.

• Google Forms. createForm, getForm, addFormQuestion, updateFormQuestion, deleteFormQuestion and listFormResponses. Google addresses a form's item only by its position, so every change reads the form first and sends the revision it read: Google refuses the write if the form changed in between instead of acting on another item. A form made by createForm is published and accepts responses as soon as it exists. The connector manifest asks for forms.body and forms.responses.readonly; every Forms method also accepts drive, so an account already connected with drive reaches Forms without being connected again. The Google Cloud project behind the OAuth client needs the Google Forms API enabled.

• Dependencies. googleapis 189, google-auth-library 11, the MCP SDK 1.32 and zod 4, so npm audit reports nothing; ESLint is gone because typescript-eslint has no fixed release.

• Packaging. The package is named cerase-google-workspace-mcp, is private on npm, and carries a connector manifest, cerase.json.

Related MCP server: worksuite-mcp

Build and run

Needs Node.js 22 or later.

npm ci
npm run build
npm prune --omit=dev
node dist/index.js

node dist/index.js auth runs upstream's browser authentication and writes tokens.json.

Test

npm test

compiles the sources and the tests into .tmp-test/, builds the bundle, and runs Node's test runner on every test. The tool handlers are called through an in-memory MCP client with the Google API clients replaced by fakes (test/helpers/mock-google-apis.ts), so no Google account is involved.

Upstream documentation

Licence

MIT, see LICENSE: upstream's copyright and licence, plus the copyright of the modifications.