Google Docs MCP Server
Google Docs, Sheets, Drive, Gmail, and Calendar integration for AI assistants.
Data last scanned today · Reviewed today
Overview
This MCP server provides a unified interface for interacting with your Google Workspace ecosystem directly through an AI client. It enables reading and manipulating data across Google Docs, Sheets, Drive, Gmail, and Calendar by leveraging standard OAuth 2.1 authentication flow. Installation is supported via local npx execution or through remote deployment on Google Cloud Run for team-wide access. Once configured, the server allows your AI to query and process documents, manage calendar events, and handle file operations within Google Drive using the provided toolset.
Our verdict
With a security score of 55/100, this server is classified as high-risk. The primary concern is the lack of a read-only mode, as every installation provides full write access to your Google account data by default. Because it is a community-maintained project rather than an official Google release and has not undergone editorial review, it should be used cautiously in environments containing sensitive information.
- Supports OAuth 2.1 for secure authentication
- Active development with commits as recent as 4 days ago
- Relies on a small footprint of 7 direct dependencies
- Large community of 44 contributors lowers bus-factor risk
- No read-only mode restricts risk mitigation
- Community-maintained project lacking official vendor support
- Requires broad scope permissions like gmail.modify
Setup
{
"mcpServers": {
"google-docs-mcp": {
"args": [
"-y",
"@a-bonus/google-docs-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
Tools
| Tool | Description | Risk |
|---|---|---|
| readDocument | Read content as plain text, JSON, or markdown | low |
| appendText | Append text to a document | medium |
| insertText | Insert text at a specific position | medium |
| deleteRange | Remove content by index range | high |
| modifyText | Replace, prepend, or transform text in a document | medium |
| findAndReplace | Find and replace text across a document | medium |
| findElement | Locate text occurrences (with index ranges) or list paragraphs/tables | low |
| listTabs | List all tabs in a multi-tab document | low |
| addTab | Add a new tab to a document | medium |
| renameTab | Rename a document tab | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What prerequisites are required in Google Cloud to use this server?
You must create an OAuth client ID with the 'Desktop app' type and enable the Google Docs, Sheets, Drive, Gmail, and Calendar APIs.
›Which Google OAuth scopes must be configured?
Your OAuth consent screen must include the gmail.modify and calendar.events scopes, along with the necessary scopes for Docs, Sheets, and Drive.
›How is the authentication token stored when running locally?
After the initial browser-based authorization process, the refresh token is saved to your local file system at ~/.config/google-docs-mcp/token.json.
›Can this server be deployed for a team to use without local installations?
Yes, you can deploy the server to Google Cloud Run using the streamableHttp transport, which allows team members to connect via a URL and handle authentication through the MCP client.
Badge
Maintain this server? Add the live badge to your README.