Workspace Connect
Google Workspace · Local MCP

Your documents.
Your coding agents.

Give Codex and Claude Code a way to work in Google Drive and Docs. One local setup. One shared Google login. Your own account.

Connect your workspace View source
workspace-connectLOCAL / STDIO

# Connect both coding agents
$ node dist/cli.js install --client both
Registered. Start fresh agent sessions.

# Check your connection
$ node dist/cli.js doctor --email you@example.com
Authenticated Drive access passed.

# Then ask your agent
“Find the project brief and update the intro.”

ILLUSTRATIVE SESSION · GOOGLE AUTH RUNS ON YOUR COMPUTER
Built for Codex + Claude CodeDrive & Docs onlyYour OAuth clientMIT licensed
01 / The connection

From a coding session
to a working document.

A small setup layer around the open-source Google Workspace MCP server. It handles local configuration; the upstream server supplies the Google tools.

01 — FIND

Work from your files.

Search Drive, list folders, and read existing Google Docs. Give your agent a document link or ask it to find the right file.

02 — WRITE

Keep the work in Docs.

Create documents, revise text, apply formatting, and work with tables and comments through the upstream MCP tools.

03 — SHARE A LOGIN

Use either agent.

Codex and Claude Code point to the same private directory. Authorize Google once, then reuse that grant locally.

02 / Get connected

A little setup.
Then, just ask.

You’ll need Node.js 24+, uv, and Codex or Claude Code. Use your own Google Cloud project with the Drive and Docs APIs enabled.

Create a Web application OAuth client with this redirect URI:

http://localhost:8769/oauth2callback

Already connected? The installer preserves existing connections. See the repository’s migration notes before changing a shared MCP configuration.

  1. Get the connector

    git clone https://github.com/zohaibarsalan/workspace-connect.git
cd workspace-connect
npm ci && npm run build

  2. Add your own OAuth client

    Download its client JSON from Google Cloud. Import it into private local storage. 

    node dist/cli.js credentials --file ~/Downloads/client.json

  3. Register your agents

    node dist/cli.js install --client both

  4. Authorize Google

    On macOS, choose your browser. Elsewhere, open the printed Google URL yourself. Restart your agent sessions after installation. 

    node dist/cli.js auth --email you@example.com --browser Zen
03 / Your data

Runs locally.
Connects directly.

The connector runs on your computer and calls Google through the upstream MCP server. OAuth credentials stay in your local configuration directory.

When an agent reads a document, its contents may be sent to that agent’s AI provider under your account settings and that provider’s terms. This public website never receives your Google login or documents.

The connector has no subscription fee. Your AI provider, Google services, storage, and platform usage remain subject to their own pricing and limits. Google OAuth apps kept in Testing require reauthorization about every seven days.

Read the full privacy notice →

Make the document part of the workflow.

Built by Zohaib Arsalan. Independent, open source, and ready to inspect.

Explore the repository