ADLS2 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| UPLOAD_ROOT | No | Root directory for file uploads | ./uploads |
| DOWNLOAD_ROOT | No | Root directory for file downloads | ./downloads |
| READ_ONLY_MODE | No | Whether the server should operate in read-only mode | true |
| AZURE_STORAGE_ACCOUNT_KEY | No | Azure ADLS2 storage account key (optional) | |
| AZURE_STORAGE_ACCOUNT_NAME | Yes | Azure ADLS2 storage account name |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesystemsA | List all filesystems in the storage account |
| create_filesystemC | Create a new ADLS2 filesystem (container) |
| delete_filesystemC | Delete an ADLS2 filesystem |
| upload_fileC | Upload a file to ADLS2 |
| download_fileC | Download a file from ADLS2 |
| file_existsB | Check if a file exists in the specified filesystem |
| rename_fileC | Rename/move a file within the specified filesystem |
| get_file_propertiesC | Get properties of a file in the specified filesystem |
| get_file_metadataC | Get metadata of a file in the specified filesystem |
| set_file_metadataC | Set a single metadata key-value pair for a file |
| set_file_metadata_jsonC | Set multiple metadata key-value pairs for a file using JSON |
| create_directoryC | Create a new directory in the specified filesystem |
| delete_directoryC | Delete a directory from the specified filesystem |
| rename_directoryB | Rename/move a directory within the specified filesystem |
| directory_existsB | Check if a directory exists in the specified filesystem |
| directory_get_pathsC | Get all paths under the specified directory |
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 16 tools
Each tool has a distinct purpose: creation, deletion, existence checks, listing, renaming, upload/download, and metadata operations. Overlaps are minimal as get, set, and set_json for metadata are clearly separated.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_directory, delete_filesystem, rename_file). No mixing of conventions.
16 tools are well-scoped for an ADLS2 server, covering filesystems, directories, files, and metadata without excessive granularity.
Covers core CRUD operations for filesystems and directories, file transfer, and metadata. Missing copy operations for files/directories, but essential workflows are present.