Google Workspace (No Cloud Console)

Gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.

Security Scan

The skill's instructions are internally inconsistent and risky: it asks you to install a third‑party npm connector that handles OAuth for wide Google Workspace access while claiming you don't need Google Cloud Console, but it provides no source, homepage, or transparency about who controls the OAuth client or what scopes/data are shared.

Purpose & Capability

The skill claims to provide Google Workspace access without using Google Cloud Console by using a third‑party package (@presto-ai/google-workspace-mcp). That can be a legitimate shortcut, but the SKILL.md does not disclose who owns the OAuth client, which Google project/framework is used, or what scopes the connector requests. The declared requirement (mcporter) is plausible as an execution shim, but its presence is not explained in the description.

Instruction Scope

Instructions tell the user to globally install an npm package and run mcporter commands that will trigger OAuth in a browser and store credentials under ~/.config/google-workspace-mcp. The doc does not list requested OAuth scopes, the OAuth client ID/owner, or whether refresh tokens are sent to a remote server. That lack of disclosure means the agent/user could be granting the package author full access to Gmail/Drive/etc. Instructions also recommend storing tokens locally and deleting them manually — no verification or transparency about remote usage.

Install Mechanism

There is no install spec in the skill bundle (instruction-only), but the SKILL.md instructs installing an npm package (global install and npx usage). Installing an unvetted npm package is a moderate to high risk action when the package source/maintainer and repository are not provided. The package name is scoped (@presto-ai) but no homepage, source repo, or publisher identity is given in the skill metadata.

Credentials

The skill itself does not request environment variables or other credentials, which would normally be good. However, the OAuth flow implied by the instructions hands over Google access to whatever OAuth client the package uses. Without disclosure of client ownership and exact scopes, this is disproportionate: you may be granting a remote third party broad, persistent access to your Google data with no visibility.

Persistence & Privilege

The skill does not request always:true or modify other skills, and it is user-invocable. Autonomous invocation is allowed by default. The main persistence consequence is local credential storage (~/.config/google-workspace-mcp) and an installed global npm package; those are normal for a connector but amplify risk if the package owner can use refresh tokens remotely.

What to consider before installing

Do not install or run this connector without more information. Before proceeding, ask the publisher for: the source code repository or package homepage, the OAuth client ID and who controls it (their Google Cloud project), and a precise list of OAuth scopes requested. Prefer using your own Google Cloud OAuth client (so tokens are under your control) or a connector with published source. If you already installed and used it, inspect ~/.config/google-workspace-mcp for tokens and revoke any issued refresh tokens via your Google account security page. Avoid running npm -g on unknown packages and verify the origin of the mcporter binary. If you cannot obtain publisher transparency, treat this skill as high-risk and do not grant it broad Google Workspace permissions.

Google Workspace Access (No Cloud Console!)

Why this skill? Traditional Google API access requires creating a project in Google Cloud Console, enabling APIs, creating OAuth credentials, and downloading client_secret.json. This skill skips ALL of that.

Uses @presto-ai/google-workspace-mcp — just sign in with your Google account and go.

Key Advantage

Traditional Approach	This Skill
Create Google Cloud Project	❌ Not needed
Enable individual APIs	❌ Not needed
Create OAuth credentials	❌ Not needed
Download client_secret.json	❌ Not needed
Configure redirect URIs	❌ Not needed
Just sign in with Google	✅ That's it

Setup (Already Done)

npm install -g @presto-ai/google-workspace-mcp
mcporter config add google-workspace --command "npx" --arg "-y" --arg "@presto-ai/google-workspace-mcp" --scope home

On first use, it opens a browser for Google OAuth. Credentials stored in ~/.config/google-workspace-mcp/

Quick Commands

Gmail

# Search emails
mcporter call --server google-workspace --tool "gmail.search" query="is:unread" maxResults=10

# Get email content
mcporter call --server google-workspace --tool "gmail.get" messageId="<id>"

# Send email
mcporter call --server google-workspace --tool "gmail.send" to="[e-mail]" subject="Hi" body="Hello"

# Create draft
mcporter call --server google-workspace --tool "gmail.createDraft" to="[e-mail]" subject="Hi" body="Hello"

Calendar

# List calendars
mcporter call --server google-workspace --tool "calendar.list"

# List events
mcporter call --server google-workspace --tool "calendar.listEvents" calendarId="[e-mail]" timeMin="2026-01-27T00:00:00Z" timeMax="2026-01-27T23:59:59Z"

# Create event
mcporter call --server google-workspace --tool "calendar.createEvent" calendarId="[e-mail]" summary="Meeting" start='{"dateTime":"2026-01-28T10:00:00Z"}' end='{"dateTime":"2026-01-28T11:00:00Z"}'

# Find free time
mcporter call --server google-workspace --tool "calendar.findFreeTime" attendees='["[e-mail]","[e-mail]"]' timeMin="2026-01-28T09:00:00Z" timeMax="2026-01-28T18:00:00Z" duration=30

Drive

# Search files
mcporter call --server google-workspace --tool "drive.search" query="Budget Q3"

# Download file
mcporter call --server google-workspace --tool "drive.downloadFile" fileId="<id>" localPath="/tmp/file.pdf"

Docs

# Find docs
mcporter call --server google-workspace --tool "docs.find" query="meeting notes"

# Read doc
mcporter call --server google-workspace --tool "docs.getText" documentId="<id>"

# Create doc
mcporter call --server google-workspace --tool "docs.create" title="New Doc" markdown="# Hello"

Sheets

# Read spreadsheet
mcporter call --server google-workspace --tool "sheets.getText" spreadsheetId="<id>"

# Get range
mcporter call --server google-workspace --tool "sheets.getRange" spreadsheetId="<id>" range="Sheet1!A1:B10"

Available Tools (49 total)

Auth: auth.clear, auth.refreshToken Docs: docs.create, docs.find, docs.getText, docs.insertText, docs.appendText, docs.replaceText, docs.move, docs.extractIdFromUrl Drive: drive.search, drive.downloadFile, drive.findFolder Sheets: sheets.getText, sheets.getRange, sheets.find, sheets.getMetadata Slides: slides.getText, slides.find, slides.getMetadata Calendar: calendar.list, calendar.listEvents, calendar.getEvent, calendar.createEvent, calendar.updateEvent, calendar.deleteEvent, calendar.findFreeTime, calendar.respondToEvent Gmail: gmail.search, gmail.get, gmail.send, gmail.createDraft, gmail.sendDraft, gmail.modify, gmail.listLabels, gmail.downloadAttachment Chat: chat.listSpaces, chat.findSpaceByName, chat.sendMessage, chat.getMessages, chat.sendDm, chat.findDmByEmail, chat.listThreads, chat.setUpSpace People: people.getUserProfile, people.getMe Time: time.getCurrentDate, time.getCurrentTime, time.getTimeZone

Troubleshooting

Re-authenticate

mcporter call --server google-workspace --tool "auth.clear"

Then run any command to trigger re-auth.

Token refresh

mcporter call --server google-workspace --tool "auth.refreshToken"

Delete credentials

rm -rf ~/.config/google-workspace-mcp