google-mcp
google-mcp
GmailおよびCalendarの読み取りツールをstdio経由で公開する、マルチアカウント対応のGoogle MCPサーバー。
セキュリティに関する注意点
credentials.jsonはローカル専用であり、決してコミットしないでください。credentials.template.jsonをcredentials.jsonにコピーし、ローカルのOAuthクライアント値を入力してください。リフレッシュトークンはソース管理ではなく、OSのキーチェーン (
keyring) に保存されます。
Related MCP server: gmail-mcp
セットアップ
依存関係のインストール:
uv sync
ローカルOAuthクライアント設定の作成:
cp credentials.template.json credentials.json
対象アカウントのメールアドレスを設定(認証の安全確認のため推奨):
export GOOGLE_MCP_PERSONAL_EMAIL="you@example.com"export GOOGLE_MCP_WORK_EMAIL="you@company.com"
必要に応じて、特定の仕事用カレンダーフィルターを設定:
export GOOGLE_MCP_WORK_CALENDAR="calendar-id-or-summary"
各アカウントの認証:
uv run auth_setup.py personaluv run auth_setup.py work
サーバーの実行
uv run server.py
統合テスト
これらは実際のGoogle APIにアクセスします。
基本的なライブテスト:
RUN_LIVE_TESTS=1 uv run integration_smoke.py
キーチェーンを破壊的に変更するテストを含める場合:
RUN_LIVE_TESTS=1 RUN_DESTRUCTIVE_TESTS=1 uv run integration_smoke.py
公開時の安全確認
ローカルセキュリティガードレールの実行:
python scripts/security_check.py
オプションのpre-commit統合:
uv tool install pre-commitpre-commit installpre-commit run --all-files
CIは
.github/workflows/security-check.ymlを通じて、すべてのプッシュ/PRで同じスクリプトを実行します。
Available Tools
4 toolscalendar_events_personalC
List events for the configured personal account calendars.
Inputs: time_min (required), time_max (required), max_results. Returns: object
calendar_events_workC
List events for the configured work account calendars.
Inputs: time_min (required), time_max (required), max_results. Returns: object
gmail_search_personalB
Search Gmail for the configured personal account.
Inputs: query (required), max_results. Returns: object
gmail_search_workC
Search Gmail for the configured work account.
Inputs: query (required), max_results. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a unique combination of service (calendar vs gmail) and account type (personal vs work), making it impossible to confuse one tool with another.
All tools follow a strict pattern: {service}_{action}_{account}, using snake_case consistently. This makes the naming predictable and easy to understand.
With 4 tools, the count is appropriate for a focused server that distinguishes between two services across two accounts, avoiding unnecessary complexity.
The tool set covers listing events and searching emails, but is limited to these read operations. Missing capabilities like creating or modifying events/schedules are notable gaps for a full Google workspace integration.
Related MCP Connectors
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
Your Gmail, Calendar, Drive, GitHub, Oura, wallet and confirmed profile facts in any MCP client.
MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.
Hosted email MCP for your own Gmail, Outlook.com, Microsoft 365, iCloud or IMAP inbox: read, search, draft, reply in thread, forward and file mail. It moves or flags up to 500 messages in one call, and a send leaves exactly one copy in Sent. A calendar is a separate connection, and connecting one adds diary and scheduling tools.
Related MCP Servers
- AlicenseAqualityCmaintenanceLocal-first Gmail MCP server using PKCE + loopback OAuth flow that stores refresh tokens in the OS keychain, enabling secure read/write Gmail access via MCP tools without tokens leaving the device.20MIT
- FlicenseNot gradedqualityDmaintenanceMulti-account Gmail MCP server for reading threads, managing labels, and creating drafts across multiple Gmail accounts.-
- AlicenseNot gradedqualityDmaintenanceA local MCP server that manages multiple Gmail accounts simultaneously, allowing MCP clients to switch between accounts per request without logging out or in. It securely stores OAuth tokens in the macOS Keychain.MIT
- AlicenseNot gradedqualityDmaintenanceA self-hostable Gmail MCP server that enables Gmail search/read, sending, replies, drafts, labels, and attachment downloads via MCP tools with OAuth authorization. Supports stdio and streamable HTTP transports.MIT