RemoteZip MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesA | Get list of files in a remote zip archive. |
| extract_fileB | Extract a specific file from a remote zip archive to local storage. |
| get_file_infoC | Get information about a specific file in the remote zip archive. |
| get_zip_statisticsB | Get statistics about the remote zip archive. |
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 4 tools
Each tool has a clear and distinct purpose: listing files, getting file info, getting archive statistics, and extracting a file. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern (extract_file, get_file_info, get_zip_statistics, list_files) with underscores, forming a predictable naming convention.
4 tools is ideal for a focused utility server that reads and extracts from remote zip archives. Each tool adds value without redundancy.
The set covers essential read operations (list, info, stats) and a single extraction action. Missing batch extraction or pattern-based extraction, but core workflows are supported.