multi-google-calendar-gmail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| accounts_listA | List connected Google accounts (alias -> email). |
| checkA | Diagnose setup: credentials file, connected accounts, and whether each account's Gmail API actually responds. |
| gmail_searchA | Search mail with Gmail's full query syntax (from:, subject:, is:unread, older_than:1y, has:attachment, ...). account is an alias, an email, or "all" for every connected account. |
| gmail_readC | Read one message's full body by the id from gmail_search. |
| gmail_labelsC | List label names for one account. |
| gmail_modifyA | Batch-modify up to 500 messages in one account: add/remove labels (created automatically if new), archive (leave the inbox), mark read. Reversible — nothing is deleted. |
| gmail_draftA | Create a draft (does NOT send). Safer default than gmail_send. |
| gmail_sendC | Send an email from one account. Always confirm with the user first. |
| calendar_listC | List calendars for one or all connected accounts. |
| calendar_eventsA | List events between two ISO dates/datetimes across one or all accounts. calendar_id defaults to each account's primary calendar. |
| calendar_create_eventA | Create an event, optionally inviting attendees by email (Google sends real invitations — confirm with the user first when inviting). |
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 11 tools
Each tool has a clear, distinct purpose. Calendar and Gmail tools are separated by prefixes (calendar_, gmail_), and actions like create, list, search, read, send are unique. No two tools overlap in functionality.
Most tools follow a (prefix)_verb_noun pattern (e.g., calendar_create_event, gmail_search). However, 'accounts_list' and 'check' break the pattern by lacking a service prefix, creating a minor inconsistency.
11 tools is well-scoped for a combined Calendar+Gmail server. It covers essential operations for both services without being excessive or too sparse.
Gmail side is fairly complete (search, read, send, draft, modify labels). Calendar side has significant gaps: it lacks update and delete for events, which would be needed for full lifecycle management.