Gmail & Google Calendar

🚀 mcp-gsuite MCP Server

An MCP server for interacting with Google products.

🚀 Quick Start

This MCP server enables interaction with Google products.

✨ Features

Currently, this MCP server supports Gmail and Calendar integration and offers the following features:

General

• Multiple Google accounts

Gmail

• Retrieve your Gmail user information.
• Search for emails using flexible queries (e.g., unread emails, emails from a specific sender, within a date range, emails with attachments).
• Retrieve the full content of an email by its ID.
• Create new draft emails, supporting recipients, subject, body, and attachments.
• Send emails.
• Delete emails.

Calendar

• Get all events from Google Calendar.
• Create new calendar events.
• Update existing calendar events.
• Delete calendar events.

📦 Installation

The MCP server can manage authentication and account information by specifying custom paths through command - line parameters:

• --gauth-file: Specify the path to the .gauth.json file containing OAuth2 client configuration. The default is the current directory.
• --accounts-file: Specify the path to the .accounts.json file containing Google account information. The default is the current directory.
• --credentials-dir: Specify the directory where authentication credentials are stored. The default is the current directory, and each account is saved separately as .oauth.{email}.json.

Example usage:

uv run mcp-gsuite --gauth-file /path/to/custom/.gauth.json --accounts-file /path/to/custom/.accounts.json --credentials-dir /path/to/custom/credentials

These options are very useful in development and testing scenarios, especially when managing multiple configurations or environments.

📚 Documentation

Build and Release

To prepare a release version:

1. Synchronize dependencies and update the lock file:

uv sync

2. Build the release:

uv build

This will create source code and wheel format distributions in the dist/ directory.

3. Publish to PyPI:

uv publish

Note: You need to set PyPI credentials via environment variables or command - line parameters:

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

Debugging

Since the MCP server runs through standard input and output, debugging can be challenging. For the best debugging experience, we highly recommend using MCP Inspector.

You can start the MCP Inspector using 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 using the following command:

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