Loading...
The mcp-gsuite server enables interaction with Google services like Gmail and Calendar, allowing read and write operations via OAuth 2.0 authentication.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The mcp-gsuite server enables interaction with Google services like Gmail and Calendar, allowing read and write operations via OAuth 2.0 authentication.
This server provides both read and write access to Google services, increasing the risk profile. It is safe when properly configured with strong OAuth credentials and appropriate account permissions, but risky if credentials are leaked or overly permissive access is granted.
Performance depends on the Google APIs' responsiveness and the size of the data being processed. Large email inboxes or calendars may result in slower response times.
Cost is primarily driven by Google API usage. Be mindful of API usage limits and potential charges for exceeding those limits.
npx -y @smithery/cli install mcp-gsuite --client claude{
"mcpServers": {
"mcp-gsuite": {
"command": "uv",
"args": [
"--directory",
"<dir_to>/mcp-gsuite",
"run",
"mcp-gsuite"
]
}
}
}gmail_get_user_infoRetrieves the Gmail user's information.
Read-only operation, no side effects.
gmail_query_emailsQueries emails based on specified criteria (e.g., unread, sender, date range).
Read-only operation, no side effects.
gmail_retrieve_emailRetrieves the content of a specific email by its ID.
Read-only operation, no side effects.
gmail_create_draftCreates a new draft email with specified recipients, subject, and body.
Creates a draft email, but does not send it immediately.
gmail_delete_draftDeletes a draft email.
Deletes an email, which could lead to data loss.
gmail_reply_to_emailReplies to an existing email, either sending immediately or saving as a draft.
Can send emails or create drafts.
calendar_get_eventsRetrieves calendar events within a specified time range.
Read-only operation, no side effects.
calendar_create_eventCreates a new calendar event with specified details.
Creates a calendar event.
calendar_delete_eventDeletes a calendar event.
Deletes a calendar event, which could disrupt scheduling.
OAuth
local
openidhttps://mail.google.com/https://www.googleapis.com/auth/calendarhttps://www.googleapis.com/auth/userinfo.emailThis server provides both read and write access to Google services, increasing the risk profile. It is safe when properly configured with strong OAuth credentials and appropriate account permissions, but risky if credentials are leaked or overly permissive access is granted.
Autonomy depends on the specific tools used and the permissions granted to the Google accounts. Exercise caution when using tools that can modify or delete data.
Production Tip
Implement robust error handling and monitoring to detect and respond to issues quickly.
The server requires OAuth 2.0 access with scopes for Gmail and Calendar, as defined in the documentation. You can review the specific scopes during the authorization process.
The server stores OAuth refresh tokens locally after you authorize the application. Ensure the server's environment is secure to protect these tokens.
Yes, the server supports multiple Google accounts. You need to configure each account in the `.accounts.json` file.
If your OAuth credentials are compromised, revoke the application's access to your Google account immediately via your Google account security settings.
Yes, the OAuth 2.0 flow supports 2FA if it is enabled on your Google account.
Monitor the server's logs for errors and activity. You can also use the MCP Inspector for debugging.
The server's access is determined by the OAuth scopes granted. You cannot limit access to specific calendars or labels within those scopes.