G Suite Integration

🚀 mcp-gsuite MCP Server

An MCP server for interacting with Google products.

🚀 Quick Start

This MCP server enables interaction with Google products, specifically supporting Gmail and Calendar integrations.

✨ Features

General

• Support for multiple Google accounts.

Gmail

• Retrieve your Gmail user information.
• Search for emails using flexible queries (e.g., unread, from a specific sender, within a date range, with attachments).
• Retrieve the full content of an email by its ID.
• Create new draft emails with options for recipients, subject, body, and CC.
• Delete draft emails.
• Reply to existing emails (either send immediately or save as a draft).
• Retrieve multiple emails by their IDs at once.
• Save multiple attachments from emails to the local system.

Calendar

• Manage multiple calendars.
• Get calendar events within a specified time range.
• Create calendar events with:
  • Title, start/end time
  • Optional location and description
  • Optional attendees
  • Support for custom time zones
  • Notification preferences
• Delete calendar events.

You can try the following example prompts:

• Get my latest unread messages.
• Search for emails from the Scrum Master.
• Get all emails from Accounting.
• View and summarize emails about ABC.
• Write a reply thanking Alice for her last email and save it as a draft.
• Reply to Bob's email with "Thank you very much" and save it as a draft.
• What's my schedule for tomorrow?
• What meetings do I have this week?
• Find all events related to Client A in my calendar.

📚 Documentation

The MCP server can be configured with options to specify custom paths for authentication and account information:

• --gauth-file: Specify the path to the .gauth.json file containing the OAuth2 client configuration. The default is ./.gauth.json.
• --accounts-file: Specify the path to the .accounts.json file containing Google account information. The default is ./.accounts.json.
• --credentials-dir: Specify the directory to store OAuth credentials after successful authentication. By default, it's in the current working directory, with a sub - directory .oauth.{email}.json for each account.

These options are particularly useful in development and testing scenarios, especially when deploying in environments that require different configurations or where the default paths are not suitable.

🔧 Technical Details

Build and Release

To prepare the distribution package:

1. Synchronize dependencies and update the lock file:

uv sync

2. Build the package distribution:

uv build

This will create source and wheel distributions in the dist/ directory. 3. Publish to PyPI:

uv publish

Note: You need to set your PyPI credentials via environment variables or command flags:

• Token: --token or UV_PUBLISH_TOKEN
• Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Debugging

Since the MCP server runs via stdio, debugging can be challenging. For the best debugging experience, we highly recommend using MCP Inspector.

You can start the MCP Inspector with the following command:

npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-gsuite run mcp-gsuite

After starting, the Inspector will display a URL that you can access in your browser to start debugging.

You can also view the server logs with the following command:

tail -n 20 -f ~/Library/Logs/Claude/mcp-server-mcp-gsuite.log