# MarkusPfundstein/mcp-gsuite [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/MarkusPfundstein/mcp-gsuite  
**GitHub Stars:** 490  
**npm Downloads (last month):** 91  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/markuspfundstein-mcp-gsuite

## Description
Integration with gmail and Google Calendar.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-gsuite": {
    "command": "npx",
    "args": ["-y","@smithery/cli"]
  }
}
```

## Documentation

## What MarkusPfundstein/mcp-gsuite MCP server does

The MarkusPfundstein/mcp-gsuite MCP server connects an MCP client to Gmail and Google Calendar. It is intended for workflows where an agent needs to inspect messages, prepare or send email responses, retrieve attachments, or work with calendar schedules.

Gmail support includes retrieving the authenticated user's information, searching mail with criteria such as unread status, sender, date range, and attachments, and fetching complete messages by ID. Agents can create and delete drafts, reply to an existing message either immediately or as a draft, retrieve several messages by ID, and save multiple email attachments to local storage.

Calendar support covers multiple calendars. The server can list events within a time range, create events with a title and start and end times, and delete events. Event creation can also include a location, description, attendees, timezone, and notification settings.

## How it works

The MarkusPfundstein/mcp-gsuite MCP server uses Google OAuth 2. The Google Cloud project must have the Gmail and Google Calendar APIs enabled, and the OAuth consent screen and client credentials must be configured. The documented scopes cover OpenID, Gmail access, Calendar access, and the user's email address.

Account metadata is stored in an accounts file. Each account can include an email address, an account type, and additional descriptive information, such as which calendar contains family events. Multiple account entries can be provided, allowing prompts to distinguish between accounts and calendars.

When a tool is first used for an account, a browser-based Google authorization flow requests the necessary permissions. After authorization, the refresh credentials are saved locally in an account-specific OAuth file and reused for later access.

## Setup and configuration

Create a `.gauth.json` file containing the OAuth client ID, client secret, redirect URI, authorization URL, and token URL. The documented local redirect URI is `http://localhost:4100/code`. Create a `.accounts.json` file containing one or more account records.

The default locations are the current directory for both configuration files and account-specific OAuth credentials. Command-line options allow these paths to be changed:

- `--gauth-file` selects the OAuth client configuration file.
- `--accounts-file` selects the account metadata file.
- `--credentials-dir` selects where authorization credentials are stored.

The README documents running the published package with `uvx mcp-gsuite`. It also provides a Claude Desktop configuration using that command. For local development, the project can be launched through `uv` from its source directory.

## Tools and capabilities

- Search Gmail using flexible query criteria.
- Read complete email content and retrieve user information.
- Create, delete, and retrieve drafts.
- Reply immediately or save a reply as a draft.
- Save multiple email attachments locally.
- Query calendar events by time range.
- Create events with attendees, locations, descriptions, timezones, and notification preferences.
- Delete calendar events.
- Work with multiple Google accounts and calendars.

## Limitations and notes

The MarkusPfundstein/mcp-gsuite MCP server currently covers Gmail and Google Calendar rather than all Google Workspace products. OAuth authorization is required before account data can be used, and the configured Google application must have access to the selected accounts.

Credentials are stored in local files by default, so deployments should choose credential and configuration paths appropriate for their environment. The server communicates over stdio, and the README recommends MCP Inspector when interactive debugging is needed. Claude Desktop is the client configuration documented in the provided material; compatibility with other clients is not established here.

_Full upstream README: https://allmcps.com/mcp/markuspfundstein-mcp-gsuite/readme_