WiseGrid MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WISEGRID_API_KEY | Yes | Create one in WiseGrid under Settings | |
| WISEGRID_BASE_URL | No | Override for self-hosted instances |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Who the current API key belongs to, its scopes, and its rate limit. Call this first if anything is failing — it distinguishes a bad key from a scope problem. |
| list_sheetsA | List sheets the API key can see. Cursor-paginated; pass the returned nextCursor to get the next page. Max limit 500. |
| get_sheetA | Get a sheet with its columns and first page of rows — one call for a usable snapshot. Use this before writing, to learn the column IDs. |
| list_columnsA | List a sheet's columns. Cell dictionaries are keyed by these column IDs as strings, so you need them before any write. |
| list_rowsA | List a sheet's rows, cursor-paginated by row id. Max limit 500. Each row carries a |
| add_rowsA | Add rows to a sheet. Each item is a dict of cells keyed by column ID (as a string), e.g. {"101": "Acme Corp", "102": "2026-09-01"}. Partial success: the response reports per-row results plus succeededCount and failedCount, so some rows can land while others fail validation. Maximum 2000 rows per call. |
| update_rowA | Update one row's cells.
|
| update_rowsA | Update many rows. Each item needs 'id', 'version' and 'cells'. NOTE: unlike update_row, bulk |
| delete_rowA | Delete a row AND ALL OF ITS CHILD ROWS. Destructive and not undoable through this API. Requires confirm=True. Read the row and its children first so you know what the subtree contains — a parent row can carry descendants that are not obvious from the row itself. |
| list_reportsB | List reports the API key can see. |
| get_reportA | Get a report's definition (its source sheets, columns and filters). |
| run_reportA | Run a report and return its rows, cursor-paginated. Max limit 500. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.