Zip MCP Server

Zip MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Zip MCP directly instead of describing what you should do. A Model Context Protocol server for ZIP compression using fastMCP and zip.js.

What you get

ZIP MCP Server is a compression server based on fastMCP and zip.js, implementing the Model Context Protocol (MCP). This project provides fully parameter-controlled ZIP compression, decompression, and query compression package information functions.

• Supports compression and decompression of files and data
• Supports multi-file packaging compression
• Provides compression level control (0-9)
• Supports password protection and encryption strength settings
• Provides query function for compressed package metadata
• Validates ZIP entry paths on decompression to prevent path traversal writes

Setting it up

The server ships on npm as zip-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Zip MCP is connected, these are the calls the assistant has available:

• Raycast — requires installing the MCP plugin
• Cursor — [https://docs.cursor.com/context/model-context-protocol#configuring-mcp-servers](https://docs.cursor.com/context/model-context-protocol#configuring-mc
• input — Path of the file or directory to be compressed (string or string array)
• output — Path of the output ZIP file
• options — Compression options (optional)
• level — Compression level (0-9, default is 5)
• password — Password protection
• encryptionStrength — Encryption strength (1-3)
• overwrite — Whether to overwrite existing files (boolean)
• Success — Text content containing success information
• Failure — Text content containing error information
• createDirectories — Whether to create non-existent directories (boolean)

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Zip MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the zip mcp mcp server does with a few real requests.

Choosing this one

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Zip MCP's toolset — Raycast, Cursor, input and 11 more — is a fair guide to whether it matches your workflow. It is maintained by 7gugu; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Zip MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.