MCP Google Workspace Integration

What is MCP Google Workspace Integration?

MCP Google Workspace Integration is an MCP (Metoro Control Protocol) tool that provides programmatic access to Google Workspace services including Google Docs, Sheets, Slides, and Drive. It is designed for developers who need to automate document creation, spreadsheet manipulation, presentation management, and file operations within Google Workspace.

How to use MCP Google Workspace Integration?

Set up a Python virtual environment, install dependencies from requirements.txt, enable the required Google APIs (Sheets, Drive, Docs, Slides), create an OAuth 2.0 client secret in Google Cloud Console, and set the MCPGD_CLIENT_SECRET_PATH and MCPGD_FOLDER_ID environment variables. Then run python main.py and use the provided MCP commands such as mcp list_files, mcp get_sheet_data, mcp create_document, or mcp create_presentation.

Key features of MCP Google Workspace Integration

• List, copy, rename files in Google Drive
• Get sheet data; add/delete rows and columns
• Update cells; create, update, delete charts
• Create documents with formatted text and headings
• Insert images, tables, and page breaks in docs
• Create presentations with slides, shapes, and speaker notes

Use cases of MCP Google Workspace Integration

• Automating generation of reports with live spreadsheet data
• Building document templates with pre-formatted text and tables
• Creating slide decks from structured data sources
• Managing a large set of files and sheets in a shared Drive folder
• Integrating Google Workspace operations into larger MCP-based workflows

FAQ from MCP Google Workspace Integration

What runtime and dependencies does it require?

Python (with virtual environment) and the packages in requirements.txt. The Google Sheets, Drive, Docs, and Slides APIs must be enabled in the Google Cloud Console.

How is authentication handled?

OAuth 2.0 – you must create a client secret in Google Cloud Console and point the MCPGD_CLIENT_SECRET_PATH environment variable to the JSON file. A token file is stored locally (default path ~/.mcp_google_spreadsheet.json) for subsequent use.

Where does user data live?

All data remains in your Google Workspace account. The only local data is the OAuth token file used to store authorization credentials.

Are there any known limits or restrictions?

The README does not mention any specific limits. Google API quotas and your Workspace plan apply.

What transport protocol does the MCP server use?

The README does not specify the transport; it relies on the MCP (Metoro Control Protocol) standard. All communication goes through Google’s API endpoints over HTTPS.