Google WorkspaceSAFE
A Model Context Protocol server for Google Workspace integration (Gmail and Calendar)
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A Model Context Protocol (MCP) server that provides tools for interacting with Gmail and Calendar APIs. This server enables you to manage your emails and calendar events programmatically through the MCP interface.
Features
Gmail Tools
list_emails: List recent emails from your inbox with optional filteringsearch_emails: Advanced email search with Gmail query syntaxsend_email: Send new emails with support for CC and BCCmodify_email: Modify email labels (archive, trash, mark read/unread)
Calendar Tools
list_events: List upcoming calendar events with date range filteringcreate_event: Create new calendar events with attendeesupdate_event: Update existing calendar eventsdelete_event: Delete calendar events
Prerequisites
- Node.js: Install Node.js version 14 or higher
- Google Cloud Console Setup:
- Go to Google Cloud Console
- Create a new project or select an existing one
- Enable the Gmail API and Google Calendar API:
- Go to "APIs & Services" > "Library"
- Search for and enable "Gmail API"
- Search for and enable "Google Calendar API"
- Set up OAuth 2.0 credentials:
- Go to "APIs & Services" > "Credentials"
- Click "Create Credentials" > "OAuth client ID"
- Choose "Web application"
- Set "Authorized redirect URIs" to include:
http://localhost:4100/code - Note down the Client ID and Client Secret
Setup Instructions
- Clone and Install:
git clone https://github.com/epaproditus/google-workspace-mcp-server.git cd google-workspace-mcp-server npm install
- Create OAuth Credentials:
Create a credentials.json file in the root directory:
{
"web": {
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET",
"redirect_uris": ["http://localhost:4100/code"],
"auth_ur8e371c2fb967OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add google-workspace-server --env GOOGLE_CLIENT_SECRET=${GOOGLE_CLIENT_SECRET} --env GOOGLE_REFRESH_TOKEN=${GOOGLE_REFRESH_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"google-workspace-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}",
"GOOGLE_REFRESH_TOKEN": "${GOOGLE_REFRESH_TOKEN}"
}
}
}
}Exposed tools (8)
3 read · 4 write · 1 destructive. Blast radius: 1 tool can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
create_event | write | Create a new calendar event |
delete_event | destructive | Delete a calendar event |
list_emails | read | List recent emails from Gmail inbox |
list_events | read | List upcoming calendar events |
modify_email | write | Modify email labels (archive, trash, mark read/unread) |
search_emails | read | Search emails with advanced query |
send_email | write | Send a new email |
update_event | write | Update an existing calendar event |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
delete_event
@google-cloud/local-auth, googleapis, @types/node, typescript
Gates applied: no_behavioural_pass.
8e371c2fb967full audit observations/trust-audit/mcp-server/epaproditus__google-workspace-2.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 8e371c2fb967 | SAFE | B | 89 | first audit |
Questions
What is the Google Workspace MCP server?
A Model Context Protocol server for Google Workspace integration (Gmail and Calendar)
What tools does Google Workspace expose?
8 in total: 3 read-only, 4 that write, and 1 that can delete or overwrite (delete_event). Every one is listed on this page with its risk.
Is Google Workspace safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B. Separately from the audit: 1 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Google Workspace need?
It reads GOOGLE_CLIENT_SECRET and GOOGLE_REFRESH_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Google Workspace run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as google-workspace-server at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (8e371c2fb967), read on 2026-10-08. The repository is watched and re-audited when it changes.