Mcp-gee-sweet MCP Server

MCP server for Google Workspace — Sheets, Drive, Docs (HTML or Markdown), and Calendar.

Local serverstdio

What is the Mcp-gee-sweet MCP Server?

Mcp-gee-sweet is an MCP integration. MCP server for Google Workspace — Sheets, Drive, Docs (HTML or Markdown), and Calendar.

Packages and local setup

The published pypi package is mcp-gee-sweet, version 0.9.1. Its declared MCP transport is stdio.

The package declares AUTH_METHOD: Pin a single auth method with no fallback, instead of the default waterfall (OAuth, then service account, then Application Default Credentials).; CREDENTIALS_PATH: Path to an OAuth Client ID JSON file downloaded from GCP Console, used for the oauth auth method.; TOKEN_PATH: Path where the OAuth token is cached after the first interactive authorization.; SERVICE_ACCOUNT_PATH: Path to a Google service account JSON key file, used for the service_account auth method.; CREDENTIALS_CONFIG: Base64-encoded service account JSON key, as an alternative to SERVICE_ACCOUNT_PATH for headless or container deployments.; ENABLED_TOOLS: Comma-separated list of tool function names to register. Default: all tools enabled..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.9.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
AUTH_METHODPin a single auth method with no fallback, instead of the default waterfall (OAuth, then service account, then Application Default Credentials).Optional
CREDENTIALS_PATHPath to an OAuth Client ID JSON file downloaded from GCP Console, used for the oauth auth method.Optional
TOKEN_PATHPath where the OAuth token is cached after the first interactive authorization.Optional
SERVICE_ACCOUNT_PATHPath to a Google service account JSON key file, used for the service_account auth method.Optional
CREDENTIALS_CONFIGBase64-encoded service account JSON key, as an alternative to SERVICE_ACCOUNT_PATH for headless or container deployments.Optional
ENABLED_TOOLSComma-separated list of tool function names to register. Default: all tools enabled.Optional