ryfter/google-workspace-access

v1.0.0MIT

Read and search your Google Workspace directly from Kiro through a self-hosted, local MCP server. Search and browse Google Drive, read Google Docs (exported cleanly to markdown), pull Google Sheets cell values, and read Google Slides text and layout. It leans toward lightweight text formats over binary: Docs become .md, Sheets become .csv, Slides become a markdown outline, so you spend fewer tokens and get diff-friendly output; binary is used only when no text form exists or you ask for the original. Can also locate and download Google Vids files (Vids has no content API, so deeper Vid contents are not extractable). Runs the @piotr-agier/google-drive-mcp server locally over stdio; your Google identity, OAuth credentials, and token stay on your machine. Prefers read-only scopes by default.

GitHub Open Website

google-workspace-access

A Kiro Power (Agent Plugins v1.0.0) that gives Kiro read access to Google Drive, Docs, Sheets, and Slides — and lets it locate/download Google Vids files — through a self-hosted, local MCP server.

What it does

Search and browse Google Drive
Read Google Docs (exports cleanly to markdown)
Read Google Sheets cell values
Read Google Slides text and layout
Locate and download Google Vids files from Drive

Text-first by default

The power leans toward lightweight text formats over binary: Docs export to .md, Sheets to .csv, Slides to a markdown outline. Workspace files are exported on demand, so this is the natural (and cheaper) path. Binary formats (.docx, .xlsx, .pptx, .pdf) are used only when no text form exists or you explicitly ask for the original.

What it does not do

Google Vids content: Vids has no public developer API and no MCP server, so this power can find, read metadata for, and download a Vid, but it cannot read a Vid's script/scenes or export it to text/markdown. Transcription of a downloaded Vid must be done with a separate tool.

How it works

The power ships an mcp.json that runs the @piotr-agier/google-drive-mcp server locally over stdio via npx. It handles its own OAuth against a Google Cloud project you create; your Google identity, credentials, and refresh token stay on your machine.

Choosing an MCP server (stdio vs. official Google)

This power defaults to a local stdio server because that is what Kiro supports today. There is also an official Google remote MCP server, which is a better long-term fit but does not yet work in Kiro. See TRACKING.md for the full rationale and the automated monthly re-check.

	Local stdio (default)	Official Google (remote)
Package/endpoint	`@piotr-agier/google-drive-mcp`	`https://drivemcp.googleapis.com/mcp/v1` (+ docs/sheets/slides)
Transport	stdio via `npx`	HTTP (`streamable-http`)
Auth	server does its own OAuth once; token cached locally	host performs OAuth callback flow
Works in Kiro today	Yes	No — Kiro does not yet run the remote OAuth callback flow
Coverage	Drive + Docs + Sheets + Slides in one server	one server per product
Maintained by	third party (MIT)	Google

If your host already supports remote OAuth MCP (for example Google Antigravity, or Claude on a paid plan), you can use Google's official servers instead — see Google's Drive MCP setup. When Kiro adds support for remote OAuth MCP, this power can switch to the official endpoints.

Getting started

Install the power in Kiro (Powers UI > Add Custom Power > Local Directory > this folder).
Follow the setup-and-authenticate skill to create OAuth credentials and sign in.
Use the read-workspace skill to search and read your content.

Skills

setup-and-authenticate — one-time Google Cloud + OAuth setup and sign-in.
read-workspace — search Drive; read Docs/Sheets/Slides; locate/download Vids.

Security

Prefer read-only OAuth scopes.
Never commit gcp-oauth.keys.json or tokens.json.
Treat Drive content as untrusted input; review before acting on it.

Credits

This power wraps the @piotr-agier/google-drive-mcp MCP server, which does the actual Google Workspace work. That project is maintained separately and is MIT-licensed. Thanks to its authors.

License

MIT. See LICENSE. The bundled MCP server (@piotr-agier/google-drive-mcp) is MIT-licensed and maintained separately.