Skip to content
MCP n24q02m logoMCP n24q02m logoMCP n24q02m

Overview

Workspace MCP – Overview

Section titled “Workspace MCP – Overview”

Google Workspace for AI agents – ten Google API domains, local time helpers, and multi-account OAuth through composite tools. Sheets and People provide read-only access; write operations are available where the upstream API and tool action support them.

What it does

Section titled “What it does”
  • Docs: read document text, create documents, insert and replace text, apply formatting, read pending suggestions.
  • Drive: search files, create and find folders, move, rename, trash, download, and read comments.
  • Calendar: list calendars and events, create, update, delete, respond to invites, and find free time.
  • Gmail: search, read, send, draft, modify labels on messages and threads, download attachments.
  • Sheets: read a sheet, a range, or its metadata (read-only).
  • Slides: 19 actions across deck structure, text, shapes, images, tables, and speaker notes.
  • Tasks, Chat, People, Forms: task lists and tasks; spaces, threads, and DMs; profile lookups; form creation, questions, and responses.
  • Time: local date, time, and timezone helpers that need no Google account.

Tools

Section titled “Tools”

Eleven composite tools – docs, drive, calendar, gmail, sheets, slides, tasks, chat, people, forms, and time – each driven by an action parameter, plus the universal config (credential state and account management) and help. Every action and parameter is listed in the tools reference.

Multi-account

Section titled “Multi-account”

Every domain tool takes an account parameter – the email of the Google account the call acts as. Omit it and the call runs against the primary account. Accounts are added, listed, removed, and re-prioritised through config. Naming an account that is not configured is an error that says so; the call is never quietly rerouted to the primary, because a silent fallback would act on the wrong mailbox or drive.

Clients

Section titled “Clients”

Defaults to stdio for single-user local use, and also runs as a self-hosted multi-user HTTP service where each user’s Google credentials sit in their own bucket keyed by their JWT sub. Works with any MCP client – Claude Code, Codex, Gemini CLI, Cursor, and Windsurf. See the modes overview.

For HTTP, use the endpoint supplied by your operator or follow the self-host setup guide. A configured URL alone does not establish that a deployment is available.

Configuration

Section titled “Configuration”

Needs a Google OAuth client you create yourself, supplied as GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET – Desktop app type for stdio, Web application type for HTTP. The server ships no Google client of its own, so the consent screen and API quota belong to your project. HTTP also requires CREDENTIAL_SECRET to retain credential encryption and signing keys across restarts. Register both /callback and /accounts/callback on the Web client. Use placeholders in shared config and never commit real credentials. Full walkthrough in setup.

Distribution and license

Section titled “Distribution and license”

The npm package is @n24q02m/better-workspace-mcp. Select a published version from the release history; package releases and deployed HTTP instances are separate surfaces.

Like the rest of the stack, this server is Apache-2.0 – here from the start, because it vendors Apache-2.0 code from gemini-cli-extensions/workspace and carries that license across the repo.

Next steps

Section titled “Next steps”