mcp-excel-reader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_excelD | – |
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 1 tool
With only one tool, there is no potential for confusion between tools. The name 'read_excel' clearly indicates its purpose, making it unambiguous.
The single tool follows a clear verb_noun naming pattern (read_excel), and there are no other tools to introduce inconsistency.
Having only one tool is too few for an Excel reader, which typically needs operations like listing sheets, reading specific ranges, or fetching metadata. This feels thin for the server's stated purpose.
The server only offers a single 'read_excel' operation, leaving gaps for specifying sheets, ranges, or handling different data formats. This is a significant limitation for a comprehensive Excel reading experience.