Excel to JSON MCP by WTSolutions
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| excel_to_json_mcp_from_dataA | Convert string format (1) tab separated Excel data or (2) comma separated CSV data to JSON. If you do not have a Pro Code, please pass only the data parameter, but not options parameter in the request |
| excel_to_json_mcp_from_urlA | Convert Excel (.xlsx) from publicly accessible URL(string format) to JSON. If you do not have a Pro Code, please pass only the url parameter, but not options parameter in the request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| from-url | Convert Excel file to JSON, the Excel file URL is publically avaliable. URL should point to .xlsx file and start with https. |
| from-url-upload | Convert Excel file to JSON, the Excel (.xlsx) file is uploaded to AI model |
| from-data | Convert Excel data to JSON data |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one converts data from a string (tab-separated Excel or CSV), and the other converts from a publicly accessible URL. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the input source.
Both tools follow a consistent naming pattern: 'excel_to_json_mcp_from_' followed by the source type ('data' or 'url'). This verb_noun style is uniform and predictable, aiding in tool identification and usage.
With only two tools, the server feels thin for a domain that might benefit from additional operations like validation, formatting options, or error handling. However, it covers the basic conversion tasks adequately, so it's borderline but not severely lacking.
The server provides core conversion functionality from both string data and URLs, which aligns with its purpose. A minor gap is the lack of tools for handling non-public URLs or advanced Excel features, but agents can work around this with the available tools for most common use cases.