@lmdat/google-sheets-oauth-mcp
Related Servers
Alternatives to @lmdat/google-sheets-oauth-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA local MCP server for creating, reading, and updating Google Sheets.7556 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Docs and Sheets that enables AI assistants to read, create, edit, style, export, and collaborate on documents using local OAuth authentication.17 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Enables reading, creating, and editing Google Docs and Sheets, managing comments, reading emails, and viewing calendar events.3425 npm17MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that lets Claude Code interact with Google Sheets, Slides, and Drive, providing tools to read/write spreadsheets, edit presentations, and manage Drive files with OAuth authentication.-
- AlicenseNot gradedqualityDmaintenanceMCP server to read, write, create, and format Google Sheets via OAuth2 authentication, providing tools for spreadsheet management.709 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP Server for Google Services, with the ability to define your own scopes and bring your own oauth key.3MIT
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: listing, appending, clearing, creating, charting, reading, writing, and managing tabs. No two tools overlap in functionality.
Most tools follow the 'sheets_<action>' pattern consistently. The only deviation is 'drive_list_spreadsheets' with a different prefix, which is acceptable given the different domain (Drive vs Sheets).
With 9 tools, the server covers essential Google Sheets operations without being overwhelming. Each tool serves a distinct and necessary function.
The tool set covers core CRUD operations (create, read, write, clear) and includes chart creation and tab management. Minor gaps like lacking a delete spreadsheet tool are acceptable for the scope.