Managing Google Workspace

What it does

When your agent uses it

• Schedule a meeting
• Update the spreadsheet
• Create a presentation
• Look up a contact

Example prompts

• “check my email”
• “find a file”
• “schedule a meeting”
• “/managing-google-workspace”

Requirements

• A credential in GOOGLE_OAUTH_CLIENT_SECRET
• Pre-approved tools (allowed-tools): Bash(uvx workspace-mcp *)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

1. 1Create OAuth credentials
2. 2Store credentials
3. 3Authenticate

What it can do on your machine

Read from SKILL.md and the folder at commit 2e9e9e7. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Bash(uvx workspace-mcp *)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • uvx

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • console.cloud.google.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • GOOGLE_OAUTH_CLIENT_SECRET

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing Google Workspace loads about 2.9k tokens when it runs, and up to ~30k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 990 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~132

When it runs · the whole SKILL.md, loaded when a task matches

~2.9k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~30k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from taylorwilsdon/google_workspace_mcp at commit 2e9e9e7, republished under its MIT licence (© taylorwilsdon). 990 words, ~2,876 tokens.

name

managing-google-workspace

description

Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search). Supports MCP tools or CLI via uvx workspace-mcp --cli. Provides tool routing, workflows, and parameter guidance for 114 tools. Triggers for "check my email", "find a file", "schedule a meeting", "update the spreadsheet", "share a doc", "create a presentation", "add a task", "look up a contact", or any mention of Google Workspace services.

allowed-tools

Bash(uvx workspace-mcp *)

user-invocable

false

uvx workspace-mcp --cli <tool_name> --args '{"user_google_email": "USER_EMAIL", ...}'

{
  "env": {
    "GOOGLE_OAUTH_CLIENT_ID": "their-client-id",
    "GOOGLE_OAUTH_CLIENT_SECRET": "their-secret"
  }
}

© taylorwilsdon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 17 other files (references) in skills/managing-google-workspace of taylorwilsdon/google_workspace_mcp.

• SKILL.md
• evaluations/edit_doc.json
• evaluations/search_email.json
• evaluations/share_file.json
• references/apps-script.md
• references/calendar.md
• references/chat.md
• references/contacts.md
• references/docs-layout-workflow.md
• references/docs.md
• references/drive.md
• references/forms.md
• references/gmail.md
• references/search.md
• references/server-options.md
• references/sheets.md
• references/slides.md
• references/tasks.md

Open the folder on GitHubat commit 2e9e9e7