Skip to main content
Glama
google-mcp

google-mcp

by giantrotta24

google-mcp

GmailおよびCalendarの読み取りツールをstdio経由で公開する、マルチアカウント対応のGoogle MCPサーバー。

セキュリティに関する注意点

  • credentials.json はローカル専用であり、決してコミットしないでください。

  • credentials.template.json を credentials.json にコピーし、ローカルのOAuthクライアント値を入力してください。

  • リフレッシュトークンはソース管理ではなく、OSのキーチェーン (keyring) に保存されます。

Related MCP server: gmail-mcp

セットアップ

  1. 依存関係のインストール:

    • uv sync

  2. ローカルOAuthクライアント設定の作成:

    • cp credentials.template.json credentials.json

  3. 対象アカウントのメールアドレスを設定(認証の安全確認のため推奨):

    • export GOOGLE_MCP_PERSONAL_EMAIL="you@example.com"

    • export GOOGLE_MCP_WORK_EMAIL="you@company.com"

  4. 必要に応じて、特定の仕事用カレンダーフィルターを設定:

    • export GOOGLE_MCP_WORK_CALENDAR="calendar-id-or-summary"

  5. 各アカウントの認証:

    • uv run auth_setup.py personal

    • uv 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-commit

    • pre-commit install

    • pre-commit run --all-files

  • CIは .github/workflows/security-check.yml を通じて、すべてのプッシュ/PRで同じスクリプトを実行します。

Available Tools

4 tools
calendar_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

    B3.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tools follow a strict pattern: {service}_{action}_{account}, using snake_case consistently. This makes the naming predictable and easy to understand.

    Tool Count5/5

    With 4 tools, the count is appropriate for a focused server that distinguishes between two services across two accounts, avoiding unnecessary complexity.

    Completeness3/5

    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

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Local-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.
      20
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Multi-account Gmail MCP server for reading threads, managing labels, and creating drafts across multiple Gmail accounts.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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