Gogcli Mcp

io.github.chrischallPublished by GitHub account chrischallv4.12.0Updated Nov 11, 2026

Google Sheets (and more) for Claude via gogcli — read, write, and manage spreadsheets

Overview

AI-generated overview

Local MCP server that gives an assistant 116 tools to read and manage Google Workspace data — Sheets, Docs, Gmail, Calendar, Drive and more — through gogcli.

What you can do
  • Read, create, update, append to, clear and find-replace in Google Sheets, and read, create and write Docs
  • Search, read, send and reply to Gmail, and list, create, update, delete and respond to Calendar events
  • List, search, move, rename, share, delete and extract text from Drive files, and export or read Slides
  • Manage Classroom courses, rosters, coursework and submissions, and Chat spaces, threads, messages and reactions
  • Run Apps Script functions and deployments, manage Tasks and Contacts, and call arbitrary Google APIs through a generic Discovery escape hatch
  • Check auth status and services, and create signed upload slots for handing files to a hosted deployment
When to use it
Useful when you want an assistant to work directly with a Google Workspace account — editing spreadsheets and documents, triaging mail, scheduling events, or organizing Drive files — from Claude Desktop or Claude Code on your own machine.
Requirements
Runs locally over stdio on desktop only. Needs Node.js 22+ and the gogcli binary installed and authenticated (for example via brew and gog auth add). GOG_ACCOUNT names the Google account; optional variables GOG_PATH, GOG_READONLY, GOG_TIMEZONE, DISPLAY_TZ and GOG_GMAIL_TRUSTED_DOMAINS adjust behavior.
Before you install
The project states it was built and is maintained by an AI coding agent and advises reviewing code and tool permissions first. Many tools write, send, share or delete data, including Gmail sends and Drive sharing and deletion; set GOG_READONLY to block mutating requests. It acts on a real Google account, and GOG_GMAIL_TRUSTED_DOMAINS changes which external recipients skip audit alerts.

Installation

In SourceWeft

  1. Open Gogcli Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

gogcli-mcp

[!WARNING] AI-developed project. This codebase was built and is actively maintained by Claude Code. Review all code and tool permissions before use.

Base Model Context Protocol server that gives Claude access to Google Workspace via gogcli. Includes 116 tools across 13 services: Sheets, Docs, Gmail, Calendar, Drive, Slides, Classroom, Chat, Apps Script, Tasks, Contacts, the generic Discovery API escape hatch, and Auth — plus hosted file uploads.

For extended Sheets or Docs support, see gogcli-mcp-sheets and gogcli-mcp-docs.

Requirements

  • gogcli installed and authenticated
  • Node.js 22+
bash
brew install gogcligog auth add [email protected]

Installation

bash
npm install -g gogcli-mcp

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "gogcli": {      "command": "gogcli-mcp",      "env": {        "GOG_ACCOUNT": "[email protected]"      }    }  }}

Claude Code

bash
claude mcp add gogcli-mcp -- gogcli-mcp

Tools (116)

ServiceToolsIncludes
Sheets8get, update, append, clear, metadata, create, find-replace, run
Docs7info, cat, create, write, find-replace, structure, run
Gmail6search, get, send, reply, reply-all, run
Calendar7events, get, create, update, delete, respond, run
Drive11ls, search, get, mkdir, rename, move, delete, share, extract-text, read-bytes, run
Slides7export, info, create, copy, list-slides, read-slide, run
Classroom25courses, students, teachers, roster, coursework, submissions (grade/return/turn-in/reclaim), announcements, topics, invitations, profile, run
Chat13spaces list/find/create, threads list, messages list/search/send, dm send/space, reactions list/create/delete, run
Apps Script8get, content, pull, create, deployments, versions, run-function, run
Tasks7lists, list, get, add, done, delete, run
Contacts5search, list, get, create, run
API3list, describe, call
Auth8list, status, health, services, add, add-url, add-complete, run
Upload1slots — signed upload URLs so a hosted caller can hand over a file (see Hosted file uploads)

All tools accept an optional account parameter to target a specific Google account.

Hosted file uploads

On a hosted deployment (mcp-host) the server shares no filesystem with you, so a path like attach, localPath, file or image names a file on the server and is refused with an explanation. To hand the server a file you hold:

  1. Call gog_upload_slots with files: [{ filename: "photo.jpg" }] (up to 10). It returns one signed upload slot per file, each with a ready curl command.
  2. PUT each file to its uploadUrl (the Content-Type must be the slot's mimeType; the URL expires after 30 minutes).
  3. Pass the slots' blobKeys to the tool that takes the file.

Each file is held to 25 MiB. It is deleted from the upload store once that call succeeds, and kept if the call fails so a retry can reuse the same keys. On a gated send (gog_gmail_send, gog_gmail_reply, gog_gmail_reply_all, gog_chat_messages_send) the confirmation preview reads the file without deleting it and binds its SHA-256, so a file re-uploaded between the preview and the approval is refused rather than sent unseen.

blobKeys is accepted by gog_gmail_send, gog_gmail_reply, gog_gmail_reply_all and gog_chat_messages_send here, and by the Gmail drafts tools and gog_gmail_import (gogcli-mcp-gmail), gog_drive_upload (gogcli-mcp-drive), the Slides image tools (gogcli-mcp-slides) and the Docs image tools (gogcli-mcp-docs). For a small file, attachInline (base64 in the call, up to 8 MiB) still works on any deployment. On a local install gog_upload_slots refuses: pass a path instead.

License

MIT

Source: packages/gogcli-mcp/README.md at commit 4302bf8

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

23
  1. v4.12.0LatestNov 11, 2026
  2. v4.10.0Nov 7, 2026
  3. v4.9.1Nov 5, 2026
  4. v4.8.1Oct 16, 2026
  5. v4.8.0Oct 12, 2026
  6. v4.7.1Oct 10, 2026
  7. v4.7.0Oct 7, 2026
  8. v4.6.3Oct 5, 2026
  9. v4.6.2Oct 5, 2026
  10. v4.6.1Oct 3, 2026
  11. v4.6.0Oct 2, 2026
  12. v4.5.2Sep 28, 2026
  13. v4.5.1Sep 25, 2026
  14. v4.5.0Sep 24, 2026
  15. v4.3.0Sep 23, 2026
  16. v4.2.5Sep 22, 2026
  17. v4.2.4Sep 21, 2026
  18. v4.2.3Sep 21, 2026
  19. v4.2.0Sep 20, 2026
  20. v4.1.0Sep 20, 2026
  21. v4.0.1Sep 18, 2026
  22. v3.0.0Sep 17, 2026
  23. v2.30.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts