Multi-account Google MCP server: Gmail, Calendar, Drive, Tasks, and Contacts
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"google-accounts-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# google-accounts-mcp One [MCP](https://modelcontextprotocol.io) server for all your Google accounts — **multi-account by design**. 51 tools across six surfaces: Gmail, a shared Google Drive folder for file handoff, a cross-MCP shared filesystem, per-account Google Calendar (incl. calendar management), Google Tasks, and Google Contacts (read/write on saved contacts). Every tool takes an `account` parameter; authorize as many Google accounts as you like and address them by name or unique substring. Built on the [Python MCP SDK](https://github.com/modelcontextprotocol/python-sdk) (FastMCP); runs as a local stdio server or a containerized Streamable HTTP service with bearer auth. Works with any MCP client. > Unofficial project, not affiliated with or endorsed by Google. ## Table of Contents - [Quick Start](#quick-start) - [Tool Reference](#tool-reference) - [Account Management](#account-management) - [Search & Read](#search--read) - [Drafts & Sending](#drafts--sending) - [Labels & Lifecycle](#labels--lifecycle) - [Attachments](#attachments) - [Drive File Store](#drive-file-store) - [Calendar](#calendar) - [Tasks](#tasks) - [Contacts](#contacts) - [Authentication](#authentication) - [Multi-Account Model](#multi-account-model) - [Configuration](#configuration) - [Architecture](#architecture) - [Development](#development) - [Testing](#testing) - [Local stdio Mode](#local-stdio-mode) - [Container Deployment](#container-deployment) - [MCP Client Registration](#mcp-client-registration) ## Quick Start One-time Google Cloud setup: create (or pick) a GCP project, enable the **Gmail, Google Drive, Google Calendar, Google Tasks, and People** APIs, and create an **OAuth client ID** of type *Desktop app* (APIs & Services → Credentials). That client ID/secret is what `authorize.py` uses for the local browser consent flow. ```bash # Prerequisites: Python 3.12+, uv uv sync export GOOGLE_CLIENT_ID=... export GOOGLE_CLIENT_SECRET=... export TOKEN_DB_PATH=~/.lo…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.