google-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUN_LIVE_TESTS | No | Set to '1' to enable basic live integration tests that hit real Google APIs. | |
| GOOGLE_MCP_WORK_EMAIL | No | Expected work account email for auth safety checks (optional but recommended). | |
| RUN_DESTRUCTIVE_TESTS | No | Set to '1' to include destructive keychain mutation tests in integration tests (requires RUN_LIVE_TESTS=1). | |
| GOOGLE_MCP_WORK_CALENDAR | No | Optional specific work calendar filter (calendar ID or summary). | |
| GOOGLE_MCP_PERSONAL_EMAIL | No | Expected personal account email for auth safety checks (optional but recommended). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gmail_search_personalB | Search Gmail for the configured personal account. |
| gmail_search_workC | Search Gmail for the configured work account. |
| calendar_events_personalC | List events for the configured personal account calendars. |
| calendar_events_workC | List events for the configured work account calendars. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.