Omniscio

Google Workspace MCP (Docs read/edit, Sheets, Drive for Claude CLI)

An MCP server that gives Claude CLI sessions direct access to Google Docs, Sheets and Drive — nineteen tools that run as a subprocess alongside the CLI, so the agent reads, searches and edits documents mid-session without Omniscio mediating each call.

On this page

Status (corrected 2026-10-22). An earlier banner here said this server was retired from session composition on 2026-09-19. It was not: the composition path stayed wired, and every session whose googleWorkspaceMcpEnabled selection is on (globally, or by a project / session override) still runs its own copy of this server — six were measured live on one machine on 2026-10-22. See How the shared .mcp.json works below for the live path. Its Enable Google Workspace Tools Settings toggle was removed on 2026-09-19; the setting behind it was not.

What it is

An MCP server that gives Claude CLI sessions direct access to Google Docs, Sheets, and Drive — 19 tools total. Unlike Omniscio's built-in Google integrations (which work through Omniscio's AI service loop), this server runs as a subprocess alongside the Claude CLI, so the agent can read, search, and edit Google Workspace documents mid-session without Omniscio mediating each call.

The primary use case is document workflows: searching for SOPs by name, reading their full contents, making batch edits (e.g. find-and-replace across sections), and working with spreadsheets — all from within a regular Claude Code session.

Where to find it

How to enable it

  1. Connect Google (if not already). Settings → Google → Connect Google. One OAuth consent covers Gmail, Calendar, Drive, Sheets, and Docs.
  2. Enable the toggle. (The Settings toggle was removed 2026-09-19; the googleWorkspaceMcpEnabled setting it wrote still turns the server on.) It used to register the google-workspace server in every new session's curated .mcp.json — a private per-session file under Omniscio's data dir, never your project folder (so it could not collide with or shadow a google-workspace server you wired into your own ~/.claude.json).
  3. GCP prerequisite. The Google Cloud project behind Omniscio's OAuth credentials must have the Google Docs API and Google Sheets API enabled. Drive API is already on. Without the Docs/Sheets APIs enabled, search and list operations work but read/edit operations return an API-not-enabled error. This is a one-time toggle in the GCP Console.

What the user sees

When you ask the agent something like "find the SOP about uploading listings and show me what's in it," the agent:

  1. Calls search_documents behind the scenes (tool call collapses in the chat)
  2. Finds matching documents with title, owner, doc ID, and last-modified date
  3. Calls read_document to pull up the full contents
  4. Presents the document text in clean markdown in the session chat

The user doesn't see raw API calls — just the formatted results. MCP tool invocations appear as collapsible activity blocks in the session transcript (same as any other Claude Code tool call like Read, Grep, or Bash).

How it behaves

Available tools (19)

Category Tool Description
Auth authenticate Authenticate with Google Workspace
check_auth_status Check current auth status
Docs — read read_document Read a full Google Doc
read_document_section Read a specific section
list_document_tabs List tabs in a document
search_documents Search across Google Docs
Docs — edit edit_section Edit a section in place
batch_edit_section Edit multiple sections in one call
insert_section Add a new section
remove_section Delete a section
find_and_replace Find and replace text in a doc
batch_find_and_replace Multiple find-and-replace in one call
Docs — create create_document Create a new Google Doc with optional initial content
Sheets create_spreadsheet Create a new Google Sheet with optional tabs and headers
read_sheet Read spreadsheet data
update_sheet_cells Update cells in a sheet
Drive list_folder_contents List files in a Drive folder
Jobs get_job_status Check status of a batch job
get_job_results Get results of a completed batch job
list_jobs List all pending/completed jobs

Differences from built-in Google integrations

Built-in Google (Calendar/Drive/Sheets) Google Workspace MCP
How it runs Omniscio's AI service loop (IPC-mediated) Claude CLI subprocess (MCP protocol)
When it's available In Omniscio's chat UI In any Claude CLI session
Document editing No (Drive: file-level ops; Sheets: cell-level) Yes (section-level Docs editing, find-and-replace)
Batch operations No Yes (batch edit, batch find-and-replace with job tracking)
Enable toggle driveEnabled, calendarEnabled, sheetsEnabled googleWorkspaceMcpEnabled (no Settings toggle since 2026-09-19)
  • google-integrations.md — the IPC-based Calendar/Drive/Sheets integrations (same OAuth)
  • drive-integration.md — the existing Drive MCP server (5 read-only tools)
  • sheets-integration.md — rich Sheets formatting and Trusted Sheets
  • cli-server-sheets-access-map.md — every road an assistant may write a sheet through, and the one approval check behind them
  • mempalace-memory.md — another MCP server composed into the same .mcp.json by the shared orchestrator

Last verified 2026-11-08