Google MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PRIVATE_KEY | No | Your Google Service Account private key | |
| GOOGLE_CLIENT_EMAIL | No | Your Google Service Account email | |
| GOOGLE_OAUTH_CLIENT_ID | No | Your Google OAuth Client ID | |
| GOOGLE_OAUTH_TOKEN_PATH | No | Path to store OAuth tokens, can be anywhere on your system | |
| GMAIL_USER_TO_IMPERSONATE | No | Email of the user to impersonate when using Service Account | |
| GOOGLE_OAUTH_CLIENT_SECRET | No | Your Google OAuth Client Secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_calendar_set_defaultC | Set the default calendar ID for operations |
| google_calendar_list_calendarsB | List all available calendars |
| google_calendar_create_eventC | Create a new event in Google Calendar |
| google_calendar_get_eventsC | Retrieve upcoming events from Google Calendar |
| google_calendar_get_eventC | Get detailed information about a specific event |
| google_calendar_update_eventC | Update an existing event in Google Calendar |
| google_calendar_delete_eventC | Delete an event from Google Calendar |
| google_calendar_find_free_timeC | Find available time slots between events |
| google_gmail_list_labelsB | List all available Gmail labels |
| google_gmail_list_emailsC | List emails from a specific label or folder |
| google_gmail_get_emailB | Get detailed information about a specific email |
| google_gmail_get_email_by_indexB | Get email by its index from the most recent search results |
| google_gmail_send_emailC | Send a new email |
| google_gmail_draft_emailC | Create a draft email |
| google_gmail_delete_emailC | Delete or trash an email |
| google_gmail_modify_labelsC | Add or remove labels from an email |
| google_drive_list_filesC | List files from Google Drive |
| google_drive_get_file_contentC | Get the content of a file from Google Drive |
| google_drive_create_fileC | Create a new file in Google Drive |
| google_drive_update_fileC | Update the content of an existing file in Google Drive |
| google_drive_delete_fileC | Delete a file from Google Drive |
| google_drive_share_fileC | Share a file with another user |
| google_tasks_set_default_listC | Set the default task list ID for operations |
| google_tasks_list_tasklistsB | List all available task lists |
| google_tasks_list_tasksC | List tasks from a task list |
| google_tasks_get_taskC | Get details about a specific task |
| google_tasks_create_taskC | Create a new task |
| google_tasks_update_taskC | Update an existing task |
| google_tasks_complete_taskC | Mark a task as completed |
| google_tasks_delete_taskC | Delete a task |
| google_tasks_create_tasklistC | Create a new task list |
| google_tasks_delete_tasklistC | Delete a task list |
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 32 tools
Every tool has a clearly distinct purpose with no ambiguity, as each is scoped to a specific Google service (Calendar, Drive, Gmail, Tasks) and a specific action on a resource (e.g., create, delete, list). Overlap is minimal, such as 'google_calendar_get_event' and 'google_calendar_get_events' being clearly differentiated by singular vs. plural.
Tool names follow a highly consistent verb_noun pattern throughout, with a clear structure: 'google_service_action_resource' (e.g., 'google_calendar_create_event'). All tools use snake_case uniformly, and verbs are predictable (create, delete, get, list, update, etc.), making the set easy to navigate.
With 32 tools, the count is borderline high for a single server, as it covers multiple Google services (Calendar, Drive, Gmail, Tasks). While each service is well-scoped individually, the overall set feels heavy and might be better split into separate servers, but it's not extreme (e.g., not 50+ tools).
The tool surface provides complete CRUD/lifecycle coverage for each Google service domain, with no obvious gaps. For example, Calendar has create, get, list, update, delete, plus utilities like find_free_time; Gmail includes send, draft, get, list, delete, and label management; ensuring agents can handle full workflows without dead ends.