Skip to main content
Glama
google-mcp

google-mcp

by giantrotta24

google-mcp

多账号 Google MCP 服务器,通过 stdio 公开 Gmail 和日历的读取工具。

安全说明

  • credentials.json 仅限本地使用,绝不能提交到版本控制中。

  • 将 credentials.template.json 复制为 credentials.json 并填入您的本地 OAuth 客户端值。

  • 刷新令牌存储在您的操作系统密钥链 (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