Google Tools MCP

What google-tools-mcp does

The google-tools-mcp MCP server gives an AI agent one MCP connection to Google Workspace services. Its tool set covers Drive, Docs, Sheets, Gmail, Calendar, Forms, Slides, Tasks, and Maps, with 160 tools available when the server starts. Drive reading includes PDFs, Word documents in .docx format, and spreadsheets.

Typical operations include searching Drive, reading document content, sending email, creating Docs or Slides, managing tasks and calendar events, building forms, and searching places. The available actions depend on the Google permissions granted during OAuth. Separate profiles can be used to keep work and personal Google accounts apart.

How it works

The google-tools-mcp MCP server uses Google OAuth rather than separate credentials for each Workspace product. On the first tool call, it opens a browser for consent and saves the resulting token at ~/.config/google-tools-mcp/token.json. Later calls reuse that authorization until consent is revoked, permissions change, or the OAuth configuration requires authorization again.

The server runs locally as a standard MCP process. It can be registered with an MCP client using the google-tools-mcp command or launched through npx -y google-tools-mcp. A shared HTTP mode is also referenced by the project, but the supplied setup instructions primarily document local stdio registration.

Setup and configuration

The guided setup starts with:

npx -y google-tools-mcp setup

The wizard helps enable the required Google APIs, configure the OAuth consent screen, create OAuth credentials, and authenticate. It can also add the server to Codex or Claude Code when their command-line tools are installed.

For manual configuration, create a Google Cloud project, enable the Docs, Sheets, Drive, Gmail, Calendar, Forms, Slides, and Tasks APIs, then create a Desktop OAuth client. Credentials can be supplied through credentials.json, a .env file, or MCP configuration environment variables. The server checks environment variables first, followed by shared and project .env files and credential files.

Install globally with npm install -g google-tools-mcp when registering the executable directly. npx is supported, but it resolves dependencies at launch and may add significant startup time. Google OAuth testing projects may require the account to be listed as a test user, and production OAuth configuration is documented for avoiding the testing setup's seven-day expiry.

Tools and capabilities

• Work with files and folders in Google Drive.
• Read PDFs, .docx files, and spreadsheets from Drive.
• Create and edit Google Docs and Slides.
• Read and update Google Sheets.
• Send and manage Gmail messages.
• Create and manage Calendar events, Google Tasks, and Forms.
• Search places through the included Maps tools.
• Select separate account profiles for different Google identities.

Limitations and notes

Access is controlled by Google OAuth and the scopes approved by the user. Revoking authorization or changing permissions can trigger another consent flow. Manual setup requires Google Cloud configuration and the relevant APIs to be enabled.

Codex registration uses the CODEX_MCP_PROTOCOL_VERSION=2026-07-28 setting in the documented configuration. Claude Code can register the server at user or project scope. The project states that it collects no telemetry and includes an open-source privacy policy, but the supplied material does not specify a license name.

The google-tools-mcp MCP server is best suited to local agents that can launch a Node-based stdio MCP process and complete browser-based OAuth. The README includes configuration examples for other MCP clients, but does not document client-specific behavior for each one.