google-mcp
google-mcp
stdio를 통해 Gmail 및 Calendar 읽기 도구를 노출하는 다중 계정 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