WiseGrid MCP
Related Servers
Alternatives to WiseGrid MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables CRUD operations on your own Google Sheets, Docs, and Drive files through any MCP client, with a token-lean design using TSV output, server-side filtering, and config-driven sheet layouts.MIT
- AlicenseNot gradedqualityCmaintenanceProvides full programmatic access to Google Sheets, enabling CRUD operations, permission management, formatting, and spreadsheet discovery through a standardized MCP interface.425 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables reading, writing, appending, and creating Google Sheets spreadsheets through MCP tools, with support for exploring spreadsheet structure and creating new sheets.191 npmMIT
- AlicenseNot gradedqualityBmaintenanceBridges MCP-compatible clients to the Google Sheets API, enabling automated spreadsheet creation, reading, writing, and formatting through natural language.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for Google Sheets that exposes tools to read cell ranges, update values, and apply advanced batch updates (borders, colors, data validation, conditional formatting) via HTTP.14 npm-
- AlicenseNot gradedqualityAmaintenanceMCP server for Google Sheets - read, write, and query spreadsheet data.160 npm2MIT
TDQS
Scored across 12 tools
Tools are clearly separated by resource and action: whoami for identity, list/get for sheets and reports, list for columns/rows, and add/update/delete for row mutations. Slight overlap exists between get_sheet (which includes rows) and list_rows, and between update_row and update_rows, but descriptions explicitly clarify the differences, minimizing misselection risk.
Names follow a consistent verb_noun pattern with list_* for collections, get_* for single entities, and action verbs (add, update, delete, run) for mutations. The special-case whoami is a standard idiom and doesn't break the overall convention.
12 tools cover the server's scope—authentication, sheet/column/row reads, row writes, and report execution—without bloat. This falls well within the ideal 3-15 range and each tool has a clear purpose.
Row lifecycle is fully covered (list, add, update single/bulk, delete), and reports can be listed, inspected, and executed. However, sheets and reports cannot be created or deleted, and there's no single-row fetch or bulk delete, leaving minor gaps for advanced workflows.