MCP Gdocs

What mcp-gdocs does

The mcp-gdocs MCP server gives an MCP client access to Google Docs, Google Drive, and Google Docs comments. Its tools cover document content, metadata, tabs, formatting, tables, images, named ranges, permissions, revisions, folders, exports, and comments. It also exposes workflow prompts for recurring tasks and a resource containing recently modified documents.

This fits the Workplace & Productivity category when an agent needs to create or maintain documents, fill templates, search a Drive, prepare exports, or coordinate review comments. Write operations commonly accept an items array for bulk work, and tools support an optional tabId for multi-tab documents.

How it works

The server uses the Google Docs and Google Drive APIs. Start it with npx -y mcp-gdocs; an MCP client launches the process when it connects. Before use, create or select a Google Cloud project and enable both APIs.

Two authentication paths are documented. OAuth is intended for personal access and provides access to the authenticated user's documents and Drive. Run npx -y mcp-gdocs auth before configuring the OAuth client, then provide GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. Service-account authentication is headless: share the relevant documents or folders with the service-account email. Google Workspace deployments can set GOOGLE_IMPERSONATE_USER for domain-wide delegation.

Setup and configuration

A service account can be configured with SERVICE_ACCOUNT_PATH, a base64-encoded CREDENTIALS_CONFIG, or GOOGLE_APPLICATION_CREDENTIALS. The README lists authentication precedence as OAuth first, followed by SERVICE_ACCOUNT_PATH, CREDENTIALS_CONFIG, and GOOGLE_APPLICATION_CREDENTIALS.

For Cursor or another MCP client, add the server as a stdio entry with npx as the command and -y mcp-gdocs as its arguments. The OAuth example uses client ID and secret environment variables; the service-account example uses a credential-file path. Service-account users must grant the account access to the documents or folders it should manage.

Tools and capabilities

Document tools can read content as text, JSON, Markdown, or a summary; insert, append, delete, and replace text; apply text, paragraph, and heading styles; update headers and footers; create footnotes; manage tabs; work with tables; insert images; convert Markdown; and create or modify named ranges. docs_batch_update groups heterogeneous document operations into one API request and supports 30 request types.

Drive tools list and search documents, create documents or folders, create documents from templates or Markdown, move, copy, rename, and trash files, export files, manage permissions, inspect revisions, and list shared drives. Comment tools list and retrieve comments, add anchored comments, reply, resolve, and delete. Prompt templates include document formatting, template filling, Markdown export, table formatting, and sharing workflows.

Limitations and notes

Access depends on the selected authentication method. A service account can work only with documents and folders shared with it unless Workspace impersonation is configured; OAuth provides the authenticated user's Drive access. Google Cloud API setup is required before connecting.

The provided configuration is for MCP clients that support the documented stdio launch command. The README specifically names Cursor and Claude Desktop, while also describing compatibility with MCP clients generally. Credential files, OAuth secrets, and encoded service-account credentials should be handled as sensitive configuration.