google-workspace-mcpGmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.
Install via ClawdBot CLI:
clawdbot install dru-ca/google-workspace-mcpRequires:
Grade Excellent — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Potentially destructive shell commands in tool definitions
rm -rf ~Audited Apr 16, 2026 · audit v1.0
Generated Mar 1, 2026
A virtual assistant that automatically schedules meetings by checking calendar availability, finding free time slots for multiple attendees, and sending calendar invites. It eliminates the back-and-forth emails typically required for scheduling.
A marketing tool that searches for specific email threads, creates email drafts, sends bulk personalized emails, and tracks responses. Useful for sales outreach, customer follow-ups, and newsletter distribution.
A system that automatically creates Google Docs from templates, inserts dynamic content, searches for existing documents, and organizes files in Drive. Ideal for teams creating standardized reports or proposals.
A solution that extracts data from Google Sheets, processes it, and generates summary reports in Docs or sends email updates. Useful for financial reporting, project tracking, and performance dashboards.
A bot that monitors Google Chat spaces, sends automated messages, manages threads, and coordinates with calendar events. Helps streamline team communication and meeting follow-ups.
Offer the Google Workspace automation as a cloud-based service with tiered pricing based on usage volume and features. Include premium support, advanced analytics, and custom integration options for enterprise clients.
Provide professional services to customize and implement the Google Workspace automation for specific business workflows. Offer training, ongoing maintenance, and workflow optimization services alongside the core tool.
License the technology to other software companies or agencies who can rebrand it as part of their own productivity suites. Provide API access and customization options for seamless integration into existing platforms.
💬 Integration Tip
Start with a single use case like email automation or calendar management before expanding to full workflow integration. Use the zero-setup OAuth to quickly demonstrate value to stakeholders.
Scored Apr 19, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Google Docs API integration with managed OAuth. Create documents, insert text, apply formatting, and manage content. Use this skill when users want to interact with Google Docs. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Docs connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Docs action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Docs examples; they add no Google Docs capability - Google Docs is not an event source, a trigger cannot read Google Docs data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).