Quick answer
The Karuzip 3.0.0 website installer includes the karuzip-mcp server. Inspect, list, and integrity-check are available out of the box. Extract, compress, image transform, and PDF actions run only inside folders you have allowed, and only after a preview step. This feature ships in the website installer; it is not included in the currently published Microsoft Store version.
We say "AI agent" deliberately: the agent your client connects to decides what to do, and Karuzip only executes and verifies. Karuzip itself never makes an autonomous decision. The formats, engine, and verification behind extract and compress are exactly the same over MCP as they are in the app.
What it can and cannot do
| Category | Operation | Default |
|---|---|---|
| Available without roots | Inspect | No write confirmation |
| Available without roots | List (default limit: 2000 entries; truncation is reported) | No write confirmation |
| Available without roots | Integrity check | No write confirmation |
| Read within allowed roots | Collect file metadata | Requires allowed roots; no write-confirmation step |
| Write within allowed roots | Extract / extract selected / compress | Preview first; confirm the same request to execute |
| Write within allowed roots | Transform an image | Preview first; confirm the same request to execute |
| Write within allowed roots | Merge / extract / split / reorder / compress PDFs | Preview first; confirm the same request to execute |
| Write within allowed roots | Image / PDF batch operations | Preview first; confirm the same request to execute |
| Available without roots | Action definitions / receipt readback / cancellation | No write confirmation |
These are the shipped interfaces in the Karuzip 3.0.0 website installer: 13 shared Actions (6 archive, 1 file collect, 1 image transform, and 5 PDF) and 21 MCP tools, including five batch tools and three management tools. Without allowed roots, only the three archive read tools and three management tools appear (6 tools).
Microsoft Store support for 3.0 is under testing with actual packages; availability has not been decided. The settings on this page apply to the Karuzip 3.0.0 website installer.
Set-up
Add Karuzip as one MCP server in your agent's configuration. The shared server definition looks like this (the karuzip-mcp command is added to PATH by the website installer; open a new terminal after installing to pick it up).
{ "mcpServers": { "karuzip": { "command": "karuzip-mcp" } } }
Claude Code
Add the karuzip server definition above to your project's or user-level .mcp.json. If Claude Code's own workspace roots are enough, leave it as is; to allow another folder as well, add --allow-root to the launch arguments.
{
"mcpServers": {
"karuzip": {
"command": "karuzip-mcp",
"args": ["--allow-root", "C:/Users/<you>/Documents"]
}
}
}
Codex CLI
Add Karuzip as an MCP server in Codex CLI's config.toml.
[mcp_servers.karuzip]
command = "karuzip-mcp"
args = ["--allow-root", "C:/Users/<you>/Documents"]
Cursor
Add the same karuzip server definition to Cursor's MCP configuration (mcp.json).
{ "mcpServers": { "karuzip": { "command": "karuzip-mcp", "args": ["--allow-root", "C:/Users/<you>/Documents"] } } }
About workspace roots
Extract and compress (the write tools) only run inside the folders the client declares as roots, or the folders you pass with --allow-root at launch. Without either form of allowed roots, the extra collection, write and batch tools do not appear: the tool list contains 6 tools instead of 21. File collection only reads metadata and does not require write confirmation; media and archive writes do. --allow-root can be repeated to allow more than one folder.
How it stays safe
- Reads are on by default; writes are limited to what you allow.Nothing is extracted or created outside the workspace roots the client declares (or a folder given at start-up). With no roots, write tools are not exposed at all.
- Writes are two-step.The first call returns only what would happen — entries, size, destination, conflict handling; the second call executes exactly that, or nothing if anything differs.
- Every run is logged.Success and failure alike land in the same processing log the app itself uses.
- Passwords never reach the agent.Encrypted archives are referenced by a name (an alias) registered in Windows Credential Manager. The password text itself never appears to the agent or in the log.
- Nothing goes over the network.
karuzip-mcpspeaks only local stdio — it does not open a listening port or make outbound connections.
Frequently asked questions
Can an agent touch my files without asking?
- Answer
No. Writes happen only inside folders you allowed, after a preview step, and every run is logged. Without allowed folders, write tools do not appear.
Does the currently published Microsoft Store version include this?
- Answer
No.
karuzip-mcpis included in the Karuzip 3.0.0 website installer; it is not included in the currently published Microsoft Store version.
Which clients work?
- Answer
Any MCP-compatible stdio client (Claude Code, Codex CLI, Cursor, etc.), by design. The shipped Karuzip 3.0.0 binary has been verified over stdio for initialize, tools/list (6 without roots / 21 with roots), and two-step confirmed extraction.
Versions and download
karuzip-mcp is bundled with the Karuzip 3.0.0+ website installer. It is not included in the currently published Microsoft Store version. It sits in the same directory as the karuzip-cli command-line tool, ready to call from any Command Prompt or PowerShell window you open after installation.
The SHA-256 hash of the 3.0.0 website installer (14.71 MB) is EFCE3B330BDF4C62EDA818957F41497B0E2F11F925AD903E8C4216D0485518F0, also listed on the Download page.
Karuzip downloads are for Windows PCs. Open this page on a Windows 10 or 11 computer to use the website installer.