multiGmailMCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gmail_list_accountsA | List all Gmail accounts that are currently authenticated and available for use. |
| gmail_searchC | Search for emails in a specific Gmail account. |
| gmail_readA | Read the full content of a specific email by ID. |
| gmail_draftC | Draft an email using a specific Gmail account. |
| gmail_sendB | Send an email using a specific Gmail account. |
| chat_list_spacesA | List Google Chat spaces (rooms and direct messages) the account belongs to. |
| chat_list_messagesB | List recent messages in a Google Chat space. |
| chat_send_messageB | Send a message to a Google Chat space, optionally as a reply within an existing thread. |
| chat_add_reactionB | Add an emoji reaction to a Google Chat message. |
| chat_get_messageA | Get the full content of a single Google Chat message by its resource name. |
| chat_delete_messageB | Delete a Google Chat message you sent. |
| chat_update_messageA | Edit the text of a Google Chat message you sent. |
| chat_list_reactionsB | List reactions on a Google Chat message. |
| chat_remove_reactionA | Remove a reaction from a Google Chat message. Use chat_list_reactions to get the reaction's resource name. |
| chat_get_attachmentA | Download an attachment from a Google Chat message. Use chat_list_messages or chat_get_message first to get the resourceName from the attachments list. |
| chat_list_membersB | List the members of a Google Chat space. |
| chat_get_spaceB | Get details about a single Google Chat space. |
| chat_create_spaceA | Create a new named Google Chat space (room), optionally inviting initial members. |
| chat_add_memberB | Add a member to a Google Chat space. |
| chat_remove_memberA | Remove a member from a Google Chat space. |
| chat_upload_attachmentB | Upload a file and send it as an attachment to a Google Chat space, with optional accompanying text. |
| gmail_get_attachmentA | Download an attachment from a Gmail message. Use gmail_read first to get the attachmentId from the attachments list. |
| gmail_read_threadA | Read all messages in a Gmail thread/conversation in chronological order. |
| gmail_replyA | Reply to an email within its existing thread. Use gmail_read to obtain the threadId, messageId (Message-ID header), and references before calling this tool. |
| gmail_forwardA | Forward an email to new recipients. Use gmail_read first to get the original message content. |
| gmail_trashB | Move an email to the trash. |
| gmail_deleteA | Permanently delete an email. This cannot be undone. Use gmail_trash to move to trash instead. |
| gmail_mark_readC | Mark an email as read. |
| gmail_mark_unreadB | Mark an email as unread. |
| gmail_starB | Star an email. |
| gmail_unstarA | Remove the star from an email. |
| gmail_list_labelsB | List all labels (folders) in a Gmail account. |
| gmail_apply_labelA | Apply a label to an email. Use gmail_list_labels to get label IDs. |
| gmail_remove_labelA | Remove a label from an email. Use gmail_list_labels to get label IDs. |
| gmail_list_draftsB | List draft emails in a Gmail account. |
| gmail_send_draftA | Send an existing draft email. Use gmail_list_drafts to get draft IDs. |
| calendar_list_calendarsB | List all calendars in a Google account. |
| calendar_list_eventsC | List upcoming events in a calendar. |
| calendar_get_eventC | Get details of a specific calendar event. |
| calendar_create_eventB | Create a new event in a Google Calendar. |
| calendar_update_eventC | Update an existing calendar event. |
| calendar_delete_eventB | Delete a calendar event. |
| calendar_quick_addB | Create a calendar event from a natural language string (e.g. 'Lunch with John tomorrow at noon'). |
| calendar_respond_to_eventA | RSVP to a calendar event invitation as the authenticated account (accept, decline, or tentative). |
| drive_list_filesB | List files and folders in Google Drive. |
| drive_search_filesC | Search for files in Google Drive. |
| drive_get_fileA | Get metadata for a specific file or folder in Google Drive. |
| drive_read_fileA | Read the text content of a file in Google Drive. Works for Google Docs, plain text, and other text-based files. |
| drive_download_fileA | Download a file from Google Drive as base64-encoded binary content. Use for images, PDFs, zips, and other non-text files. Google Docs/Sheets/Slides are exported to a concrete format (default PDF). |
| drive_upload_fileC | Upload a file to Google Drive. |
| drive_create_folderB | Create a new folder in Google Drive. |
| drive_delete_fileA | Delete a file or folder from Google Drive (moves to trash). |
| drive_share_fileB | Share a file or folder with another user. |
| drive_move_fileB | Move a file or folder to a different folder in Google Drive. |
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 54 tools
Tools are clearly separated by domain-specific prefixes (gmail_, calendar_, chat_, drive_), making each tool's purpose immediately identifiable. Within each domain, operations are distinct, and descriptions provide enough detail to differentiate similar actions like gmail_delete vs gmail_trash or gmail_star vs gmail_unstar.
All tool names follow a consistent 'domain_verb_noun' pattern (e.g., gmail_send, calendar_list_events). While verbs like 'read' and 'get' are used for different actions, they are contextually appropriate and not confusing.
With 54 tools, this server is large but justified by covering four distinct Google services. Some tools like gmail_star/unstar or mark_read/unread could be combined, but the count is still reasonable for a comprehensive multi-service MCP.
The tool set provides extensive coverage for Gmail, Calendar, Chat, and Drive, including CRUD operations, search, attachments, and more. Only minor gaps like drive update file exist, but core workflows are fully supported.