JSON to Excel 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 |
|---|---|
| json_to_excel_mcp_from_urlB | Convert JSON data from publicly accessible URL(.json format) to CSV data. If you do not have a Pro Code, please pass only the url parameter, and do not pass the options parameter. |
| json_to_excel_mcp_from_dataA | Convert JSON data to CSV data. If you do not have a Pro Code, please pass only the data parameter, and do not pass the options parameter. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| from-url | Convert JSON file to CSV data, the JSON file URL is publically avaliable. URL should point to .json file and start with https. |
| from-url-upload | Convert JSON file to CSV data, the JSON file is uploaded to AI model |
| from-data | Convert JSON data to CSV 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 processes JSON data directly, while the other fetches JSON from a URL before conversion. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern with 'json_to_excel_mcp_from_' prefix, differentiated by 'data' and 'url' suffixes. The naming is perfectly uniform and predictable.
Two tools are borderline for a JSON-to-Excel conversion server, as it feels thin but covers the basic input methods (direct data and URL). It's reasonable but could benefit from additional tools like format customization or batch processing.
The server covers the core conversion functionality from JSON to CSV (implied Excel format) for both data and URL inputs, with minor gaps such as lack of output format options or error handling tools, but agents can work around these.