MCP Google Sheets
Related Servers
Alternatives to MCP Google Sheets
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for interacting with Google Sheets, providing tools to list sheets, read data from cell ranges, and write data to cell ranges.33MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables reading from and appending to Google Sheets using a service account, with tools to find sheets, read ranges, and append rows, plus an audit log.27 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server to read, write, create, and format Google Sheets via OAuth2 authentication, providing tools for spreadsheet management.425 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Google Sheets - read, write, and query spreadsheet data.157 npm2MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Google Sheets through natural language, allowing users to create, read, update, and manage spreadsheet data via the Google Sheets API v4.-
- AlicenseBqualityDmaintenanceA local MCP server for creating, reading, and updating Google Sheets.7157 npmMIT
TDQS
Scored across 10 tools
Each tool targets a distinct operation: adding rows/columns, creating/renaming sheets, deleting rows, finding rows, reading data/schema/info, and updating rows. Even find_rows and get_sheet_data have clear differences (search vs read range).
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., add_columns, delete_rows, get_sheet_data). The naming is predictable and clear.
With 10 tools, the server covers the core operations for Google Sheets without being overwhelming or too sparse. Each tool serves a clear purpose in spreadsheet management.
The tool set covers create, read, update, and delete operations for rows, columns, and sheets. Minor gaps exist (e.g., no delete_columns or delete_sheet), but the main workflows are supported, and agents can work around missing operations.