An MCP server that reads and writes spreadsheet data to MS Excel file
Excel MCP server has 6 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-80 chars, mostly adequate) and input schemas with type definitions. However, output schemas are completely undocumented, LLMs cannot predict what fields to expect from responses. Parameter descriptions are minimal and lack format/constraint guidance. No error handling guidance, no pagination metadata in responses, and no tool annotations (readOnlyHint/destructiveHint). Naming is clear and verb-based (read_*, write_*), but parameter naming lacks consistency (fileAbsolutePath vs sheetName mixing camelCase/snake_case). The server supports both STDIO and HTTP/SSE transports, but STDIO limits remote accessibility.
Read data from Excel sheet with pagination.
Read formulas from Excel sheet with pagination.
[Windows only] Read data as an image from the Excel sheet with pagination.
List all sheet names in an Excel file
Write data to the Excel sheet
Write formulas to the Excel sheet
Output schemas completely undocumented. LLMs cannot predict response structure, field types, or what data is available for downstream tool calls. This violates pattern:tool and forces agents to guess.
No error handling guidance. Tools lack recovery hints (e.g., 'File not found. Verify the absolute path exists.' or 'Invalid range format. Use A1:C10.'). Agents cannot self-correct on failures.
Pagination parameters (range, knownPagingRanges) lack format constraints and examples. Descriptions do not explain pagination strategy, default behavior, or how to iterate. LLMs cannot reliably paginate large sheets.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe read operations from destructive writes without reasoning about tool names. Violates current MCP spec (2026-07-28).
Parameter naming inconsistency: fileAbsolutePath (camelCase) vs sheetName (camelCase) vs range (snake_case intent). Inconsistent casing and lack of type suffixes (e.g., file_path vs fileAbsolutePath) reduce clarity.