zipnative MCP — ZIP creation, inspection, secure extraction & verification

What this does

zipnative MCP — ZIP creation, inspection, secure extraction & verification exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

ZIPNATIVE_MCP_OUTPUT_DIR
ZIPNATIVE_MCP_CACHE_DIR
ZIPNATIVE_MCP_PORT
ZIPNATIVE_MCP_HTTP_TOKEN
ZIPNATIVE_MCP_MAX_UNCOMPRESSED_BYTES
ZIPNATIVE_MCP_MAX_ENTRIES
ZIPNATIVE_MCP_WORKERS
ZIPNATIVE_MCP_MAX_FILE_OUTPUT_BYTES

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install zipnative MCP — ZIP creation, inspection, secure extraction & verification?

Run the Claude Code command in the install section to add zipnative MCP — ZIP creation, inspection, secure extraction & verification to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with zipnative MCP — ZIP creation, inspection, secure extraction & verification?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to zipnative MCP — ZIP creation, inspection, secure extraction & verification as well.

Does zipnative MCP — ZIP creation, inspection, secure extraction & verification need an API key?

Yes. Before it can run, set these environment variables: ZIPNATIVE_MCP_OUTPUT_DIR, ZIPNATIVE_MCP_CACHE_DIR, ZIPNATIVE_MCP_PORT, ZIPNATIVE_MCP_HTTP_TOKEN, ZIPNATIVE_MCP_MAX_UNCOMPRESSED_BYTES, ZIPNATIVE_MCP_MAX_ENTRIES, ZIPNATIVE_MCP_WORKERS, ZIPNATIVE_MCP_MAX_FILE_OUTPUT_BYTES. They go in the env block of your MCP config.