Dynamic Excel MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | No | Optional API key for authentication (used when TRANSPORT_MODE is 'http') | |
| HTTP_HOST | No | Host for HTTP server (required when TRANSPORT_MODE is 'http') | 0.0.0.0 |
| HTTP_PORT | No | Port for HTTP server (required when TRANSPORT_MODE is 'http') | 3000 |
| LOG_LEVEL | No | Logging level | info |
| S3_BUCKET | No | S3 bucket name (required when STORAGE_TYPE is 's3') | |
| AWS_REGION | No | AWS region (required when STORAGE_TYPE is 's3') | |
| STORAGE_TYPE | No | Storage type: 'local' for local file system, 's3' for AWS S3 | |
| TRANSPORT_MODE | No | Transport mode: 'stdio' for local MCP client mode, 'http' for remote server mode | stdio |
| ALLOWED_ORIGINS | No | CORS allowed origins (required when TRANSPORT_MODE is 'http') | * |
| DEV_STORAGE_PATH | No | Path for local file storage | ./temp-files |
| AWS_ACCESS_KEY_ID | No | AWS access key ID (required when STORAGE_TYPE is 's3') | |
| PRESIGNED_URL_EXPIRY | No | Expiry time for presigned URLs in seconds (used when STORAGE_TYPE is 's3') | 3600 |
| AWS_SECRET_ACCESS_KEY | No | AWS secret access key (required when STORAGE_TYPE is 's3') |
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 |
|---|---|
| generate_excelA | Generate an Excel file from a structured JSON schema. Use this tool when the user wants to:
The tool accepts a JSON schema describing the structure, data, and formatting of the Excel file. Supported features:
Layout types:
|
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 possibility of confusion or overlap between tools. The single tool 'generate_excel' has a clear and distinct purpose focused on creating Excel files from JSON schemas.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'generate_excel' follows a clear verb_noun pattern, and there are no other tools to create inconsistencies.
A single tool for a server named 'Dynamic Excel MCP Server' feels thin and under-scoped. While the tool is feature-rich, the domain suggests operations like reading, updating, or analyzing Excel files, which are missing. This limits the server's utility for comprehensive Excel interactions.
The server is severely incomplete for its implied domain of dynamic Excel operations. It only supports generation from JSON schemas, lacking essential CRUD operations such as reading existing files, updating data, or performing analyses. This creates significant gaps that will hinder agent workflows involving Excel beyond initial creation.