2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill google-workspace-mcp- _meta.json307 B
- SKILL.md4.5 KB
Overview
This skill provides direct access to Gmail, Calendar, Drive, Docs, Sheets, Slides, Chat, and People without creating a Google Cloud Console project or manual OAuth setup. It uses a packaged OAuth flow so you sign in with your Google account once and credentials are stored locally. The result is a fast, low-friction integration for archiving, backup, automation, and ad-hoc queries.
How this skill works
The skill wraps the @presto-ai/google-workspace-mcp client to perform Google Workspace API operations after a simple browser-based OAuth sign-in. On first use it opens a consent screen and saves tokens under ~/.config/google-workspace-mcp so you can run commands from the command line or an orchestrator. Tools cover email search/send, calendar events and free-time finding, Drive file search/download, Docs/Sheets/Slides reads and edits, Chat interactions, and basic People/time utilities.
When to use it
- You want Google Workspace access without creating a Cloud Console project or managing client_secret.json.
- You need a quick way to archive or back up emails, documents, calendars, or Drive contents.
- You are building scripts or automation that require OAuth but want zero setup overhead.
- You need to inspect, export, or search workspace content from the CLI or an automated job.
- You need to prototype integrations before committing to full Google Cloud setup.
Best practices
- Use a dedicated Google account or service account-like account for automated backups to limit scope and data mix.
- Run interactive commands initially to complete OAuth and verify permissions before automating repetitive jobs.
- Store downloaded credentials and backups on encrypted storage and restrict local file permissions.
- Use query filters (e.g., Gmail search, Drive query) to limit data volume and API calls during exports.
- Refresh or clear auth tokens when rotating credentials or transferring access to another machine.
Example use cases
- Export unread or labeled Gmail messages for long-term archival or e-discovery workflows.
- Search Drive for budget or contract files and download matches into a local backup repository.
- Create and update Docs or Sheets programmatically as part of a reporting pipeline.
- List calendar events, create meetings, or find common free time across attendees for scheduling automation.
- Send notifications or DMs to Google Chat spaces or individuals from monitoring scripts.
FAQ
No. The packaged client handles required scopes and the OAuth redirect flow so you only sign in once via the browser.
Where are credentials stored and how do I re-authenticate?
Credentials are saved in ~/.config/google-workspace-mcp. To re-authenticate, run auth.clear and trigger any command to reopen the consent flow; auth.refreshToken will refresh tokens if needed.