概览
What is ZIP MCP Server?
ZIP MCP Server is a compression server built on fastMCP and zip.js that implements the Model Context Protocol (MCP). It provides fully parameter-controlled ZIP compression, decompression, and query of compressed package information for AI clients.
How to use ZIP MCP Server?
Install globally via npm (npm install -g zip-mcp), then add the server to your MCP JSON configuration with the command zip-mcp. After configuration, AI clients (e.g., Claude, Raycast, Cursor) can call its tools (compress, decompress, getZipInfo, echo) through the MCP protocol.
Key features of ZIP MCP Server
- Compression and decompression of files and data
- Multi-file packaging compression
- Compression level control (0–9)
- Password protection and encryption strength settings (1–3)
- Query function for compressed package metadata
- Validates ZIP entry paths to prevent path traversal writes
Use cases of ZIP MCP Server
- Compress local files or directories into a password-protected ZIP archive
- Decompress ZIP files to a specified directory with overwrite control
- Inspect metadata (file count, sizes, compression ratio) of a ZIP file
- Test MCP connectivity via the echo tool
FAQ from ZIP MCP Server
What runtime does ZIP MCP Server require?
It is installed via npm, so Node.js is required. The README does not specify a minimum version.
Can I password-protect a ZIP archive?
Yes. The compress tool accepts an optional password parameter and an encryptionStrength parameter (1–3).
Where does the server read and write files?
All operations are on local files as specified by the input and output parameters. No remote storage is involved.
How does the server prevent arbitrary file writes during decompression?
Starting from version 1.0.6, extraction validates each ZIP entry path against the output root, rejecting absolute paths, drive-letter paths, .. segments, and any path that would escape the output directory.
What transport does the MCP server use?
The server is configured via a JSON entry with a command (zip-mcp) and no explicit transport arguments, implying it uses standard input/output (stdio) transport as typical for MCP servers.
