zipnative MCP — ZIP creation, inspection, secure extraction & verification
Local ZIP toolkit for MCP clients: create, inspect, verify and safely extract archives
- Pricing
- Open source
- Platforms
- CLI, self-hosted, Linux
- Runs
- Locally
- Version
- 1.1.0
- Listing updated
- today
Similar MCP servers
About zipnative MCP — ZIP creation, inspection, secure extraction & verification
zipnative MCP — ZIP creation, inspection, secure extraction & verification is an open-source MCP server for files and documents. It runs locally on your machine and is started by your AI client.
Fifteen tools handle ZIP work on a machine with no network access at all. The README stresses that the server has no network code path, no telemetry and never fetches a URL from an argument. It runs on the zero-dependency zipnative engine, which the README says is validated against ISO/IEC 21320-1 in CI, and ships seven prompts alongside the tools.
Extraction is secure by default: zip-slip and device names, symlinks, duplicate paths, size and ratio bombs and overlapping entries are refused with fixed ZIP_ error codes, and relaxations are explicit named inputs. File output is confined to one sandbox directory set by ZIPNATIVE_MCP_OUTPUT_DIR; if it is unset, every tool works on base64 only. Operators can also cap uncompressed size, entry counts, worker threads and file output size.
Beyond extraction, it can build reproducible archives, change one without recompressing anything, rewrite archives from Gradle, Maven or 7-Zip into a canonical deterministic form, and merge up to 32 sources. It installs from npm over stdio, with an optional loopback HTTP mode protected by a bearer token.
Install
Run in a terminal
claude mcp add zipnative-mcp --env ZIPNATIVE_MCP_HTTP_TOKEN='<ZIPNATIVE_MCP_HTTP_TOKEN>' -- npx -y zipnative-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"zipnative-mcp": {
"command": "npx",
"args": [
"-y",
"zipnative-mcp"
],
"env": {
"ZIPNATIVE_MCP_HTTP_TOKEN": "<ZIPNATIVE_MCP_HTTP_TOKEN>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"zipnative-mcp": {
"command": "npx",
"args": [
"-y",
"zipnative-mcp"
],
"env": {
"ZIPNATIVE_MCP_HTTP_TOKEN": "<ZIPNATIVE_MCP_HTTP_TOKEN>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"zipnative-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"zipnative-mcp"
],
"env": {
"ZIPNATIVE_MCP_HTTP_TOKEN": "<ZIPNATIVE_MCP_HTTP_TOKEN>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"zipnative-mcp": {
"command": "npx",
"args": [
"-y",
"zipnative-mcp"
],
"env": {
"ZIPNATIVE_MCP_HTTP_TOKEN": "<ZIPNATIVE_MCP_HTTP_TOKEN>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"zipnative-mcp": {
"command": "npx",
"args": [
"-y",
"zipnative-mcp"
],
"env": {
"ZIPNATIVE_MCP_HTTP_TOKEN": "<ZIPNATIVE_MCP_HTTP_TOKEN>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
ZIPNATIVE_MCP_OUTPUT_DIRAbsolute path of the one sandbox directory: zipPath / sourcePath inputs are read from it and outputMode='file' / outputDir outputs are written under it (never overwritten; the real path of every file read and of every parent written must stay inside — a planted symlink or junction is SECURITY_VIOLATION). Unset: every tool works on base64 only (no file I/O beyond the opt-in cache).ZIPNATIVE_MCP_CACHE_DIROpt-in content-addressed response cache directory (absolute path) (SHA-256 keyed, 1h TTL, 256 MiB, oldest-written evicted first, plaintext at rest). Never caches zipPath / sourcePath inputs, file output, defaultDate='now', parallel, describe_engine or draft_governance_issue.ZIPNATIVE_MCP_PORTServe Streamable HTTP on this loopback port (POST /mcp) instead of stdio (MCP 2026-07-28, stateless, legacy fallback). Unauthenticated unless ZIPNATIVE_MCP_HTTP_TOKEN is set.ZIPNATIVE_MCP_HTTP_TOKENOpt-in bearer token for the HTTP transport (>= 16 chars, no whitespace; a weaker value refuses to start). When set, /mcp requires 'Authorization: Bearer <token>' or answers 401. Compared constant-time, never logged.ZIPNATIVE_MCP_MAX_UNCOMPRESSED_BYTESOperator ceiling for limits.maxEntryUncompressedSize, limits.maxTotalUncompressedSize and limits.maxEntryCompressedSize in bytes (default 8589934592 = 8 GiB, the engine default). Integer >= 1024, read once at startup; an invalid value refuses to start. A per-call value above it is refused with LIMIT_CEILING_EXCEEDED.ZIPNATIVE_MCP_MAX_ENTRIESOperator ceiling for limits.maxEntries and scan_zip_forward maxEntries (default 100000, the engine default; the scanner's default budget of 10000 is clamped to it, only an explicit value above it is refused). Integer >= 1, read once at startup; an invalid value refuses to start.ZIPNATIVE_MCP_WORKERSOperator ceiling for create_zip parallel.workers (default 8; with no explicit workers the engine default max(1, min(cores - 1, 8)) applies, bounded by this ceiling; 0 disables worker threads and keeps compression on the calling thread). Integer >= 0, read once at startup; an invalid value refuses to start.ZIPNATIVE_MCP_MAX_FILE_OUTPUT_BYTESOperator ceiling for every file written in outputMode='file' (create_zip, modify_zip, canonicalize_zip, merge_zip, extract_zip, inflate_raw), enforced while streaming (default 4294967296 = 4 GiB, the 1.0.0 behaviour). Integer >= 1048576, read once at startup; an invalid value refuses to start. Raise it to write Zip64 archives above 4 GiB into the sandbox (create_zip stream entries with zip64: true).
Tools this server provides (15)
Taken from the project documentation; the running server may differ.
- inspect_zip
- One-call archive report with sizes, counts, flags and a determinism verdict.
- list_zip_entries
- Paged central-directory inventory without decompressing.
- read_zip_entry
- Reads one entry by name or index without extracting.
- verify_zip
- Deep verification of structure, CRC-32 and sizes.
- extract_zip
- Secure-by-default extraction inline or into the sandbox.
- scan_zip_forward
- Walks local headers of truncated or unseekable streams.
- sanitize_entry_paths
- Maps names to safe relative paths or reports the rule that fired.
- create_zip
- Writes a ZIP from inline text, base64 or sandbox files.
- modify_zip
- Adds, replaces, removes or renames entries without recompressing.
- canonicalize_zip
- Rewrites an archive into canonical deterministic form.
- merge_zip
- Merges 1 to 32 archives without recompressing.
- compute_crc32
- Computes the ZIP CRC-32 of text, base64 or a file.
- inflate_raw
- Raw DEFLATE decompression with a mandatory output bound.
- describe_engine
- Offline report of versions, limits, codecs and error codes.
- draft_governance_issue
- Drafts a GitHub issue locally for a human to submit.
What it does
- Secure extraction
- Refuses zip-slip, symlinks, duplicates and decompression bombs by default.
- One-call inspection
- Reports sizes, counts, Zip64, encryption flags and a determinism verdict, and can act as a CI gate.
- Reproducible creation
- Builds archives in canonical order with fixed timestamps, optionally byte-identical across runtimes.
- Modify without recompressing
- Adds, replaces, removes or renames entries while keeping payloads untouched.
- Merge and canonicalize
- Combines up to 32 archives or normalises one into a deterministic form.
- Truncated-stream scanning
- Walks local headers to list entries from a cut-off download.
- Sandboxed file output
- Writes only inside one configured directory and rejects planted symlinks.
Good for
- Check an untrusted ZIP for traversal or bomb risks before extracting
- Make build artifacts reproducible for CI comparison
- Read a single file from a large archive without unpacking it
- Merge several archives without recompression
- Recover an entry listing from a partially downloaded ZIP
Pricing
Open source
Open source npm package; no fees mentioned
zipnative MCP — ZIP creation, inspection, secure extraction & verification FAQ
Does it make network requests?
No. The README says there is no network code path, no telemetry and no URL fetching.
Where can it write files?
Only under the directory named by ZIPNATIVE_MCP_OUTPUT_DIR; without it, tools work on base64 only.
How many tools does it have?
Fifteen, including inspect_zip, extract_zip, create_zip, merge_zip and verify_zip.
Can it run over HTTP?
Yes, on a loopback port via ZIPNATIVE_MCP_PORT; setting ZIPNATIVE_MCP_HTTP_TOKEN requires a bearer token.
Is zipnative MCP — ZIP creation, inspection, secure extraction & verification free?
Yes. zipnative MCP — ZIP creation, inspection, secure extraction & verification is open source, so you can use and self-host it for free.
How do I add zipnative MCP — ZIP creation, inspection, secure extraction & verification to Claude Code?
Run this command in your terminal: claude mcp add zipnative-mcp --env ZIPNATIVE_MCP_HTTP_TOKEN='<ZIPNATIVE_MCP_HTTP_TOKEN>' -- npx -y zipnative-mcp
What are the best alternatives to zipnative MCP — ZIP creation, inspection, secure extraction & verification?
The closest alternatives to zipnative MCP — ZIP creation, inspection, secure extraction & verification are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


