原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Ziplark

作者:zhitongblog版本 0.6.0i★ 22i在你的电脑上运行官方网站 ↗
注册名称io.github.zhitongblog/ziplark

安装方法

What it does

Archive server: grep, read, extract, edit, convert & create ZIP, 7z, tar, RAR, ISO, DEB, RPM, CAB.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度16/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分28/100

质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 下载开发者的安装文件

    下载作者的 .mcpb 文件

    .mcpb 文件直接来自开发者,我们没有修改

  2. 双击文件,然后在电脑版 Claude 应用中点击 Install

  3. 试一试

    用 Ziplark 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Ziplark,或回答中出现 Ziplark 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Ziplark

Ziplark 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 Ziplark 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

B · 其他 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Ziplark

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Ziplark 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

Cursor 暂时无法连接 Ziplark

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Ziplark 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

VS Code 暂时无法连接 Ziplark

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 Ziplark 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Ziplark 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
连接方式
在你的电脑上运行
最新版本i
0.6.0
分类i
其他
发布到注册中心i
2026年11月14日
代码最后更新i
2026年11月15日
作者
zhitongblog
软件包
mcpb: …/ziplark-mcp-0.6.0.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 zhitongblog 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于4天前

  • ✓ 通过

    有许可证

    使用 MIT

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/zhitongblog-ziplark.svg)](https://mcp.popnx.com/en/servers/zhitongblog-ziplark)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20749 个服务器的 97%
  • 发布到注册中心的时间比此分类中其他 20749 个服务器的 89% 更新
  • 基础检查结果等于或优于此分类中其他 20749 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Ziplark 安全吗?

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于4天前,最新版本(0.6.0)于5天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582414个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
Ziplark
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置需要安装在电脑上在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查3/34/44/44/41/44/4
许可证MITAGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Free, fast, cross-platform archiver. Extracts ZIP, RAR (incl. RAR5), 7z, tar, ISO and the common compressed-tar variants; creates ZIP (with AES-256), 7z and tar archives. One small Rust engine, three ways to drive it: a desktop app, a CLI, and an MCP server.

Download · Website · by doaipm · Report a bug

Install

# macOS — Homebrew

brew install --cask zhitongblog/tap/ziplark # desktop app brew install zhitongblog/tap/ziplark # CLI + MCP (ziplark, ziplark-mcp)

# Windows — Scoop (CLI + MCP)

scoop bucket add ziplark https://github.com/zhitongblog/scoop-bucket scoop install ziplark

Or grab a build for any platform from the releases page (macOS .dmg, Windows .msi/.exe, Linux .deb/.AppImage, and CLI archives).

Read / Extract / PreviewCreate / AppendEncryption
ZIP (incl. .zip.001, .z01+.zip, .jar, .apk, .ipa, .whl, .nupkg, .crx, .epub, .docx, .cbz)✅✅AES-256 (read ZipCrypto)
7z (incl. .7z.001 multi-volume, .cb7)✅✅AES-256
RAR / RAR5 (incl. multi-volume, SFX, .cbr)✅—reads encrypted, incl. encrypted headers
tar (.tar, .cbt)✅✅—
tar.gz / .bz2 / .xz / .zst / .lz4✅✅—
gz / bz2 / xz / zst / lz4 (single stream)✅✅ (create)—
ISO 9660 / Joliet (.iso)✅——
Debian & Unix ar (.deb, .udeb, .ipk, .ar, .a)✅——
RPM & CPIO (.rpm, .cpio, .cpio.gz/.xz/.zst/.bz2/.lz4)✅——
macOS Installer & XAR (.pkg, .mpkg, .xar, .xip)✅——
Microsoft Cabinet (.cab, Store + MSZIP)✅——

RAR, ISO, DEB/AR, RPM/CPIO, PKG/XAR and CAB are read/extract/preview formats — all

parsed in memory-safe Rust (except RAR, which uses the official UnRAR C++

library). ZIP, 7z and tar variants support full creation (including --split

multi-volume .001, .002, … output) and in-place modification (add, mv, rm).

RAR, properly

RAR is the format people *arrive* with — a download split into volumes, packed solid, sometimes one volume short — so it gets first-class treatment rather than a checkbox:

  • A volume set is one archive. movie.part03.rar, or the older movie.r01, opens the whole set: any file of the set resolves to the first volume, the parts are listed, and an entry that spans volumes comes out whole. Both naming schemes are handled, including the legacy one whose first volume is movie.rar rather than movie.r01.
  • A missing volume is named. Ziplark says *which* file it needs next instead of failing with a generic error, and refuses to start writing rather than stopping half-way.
  • Damage is survivable. --keep-broken (in the app: "Extract what's readable") gets every intact file out of a damaged or incomplete archive and reports exactly which entries failed and which were written incomplete. Verifying reports *every* bad entry, so you know which file to re-download.
  • Verifying writes nothing. Integrity is checked by decompressing each entry and discarding the bytes — not, as a surprising number of tools do, by extracting the whole archive to a temporary directory.
  • Metadata survives. Permissions (an executable stays executable), 100-nanosecond RAR5 timestamps, symlinks as symlinks, per-entry compressed sizes, solid/recovery-record/lock flags, and the archive comment.
  • Encrypted headers work. An archive whose *file names* are encrypted (rar -hp) lists and extracts with a password like any other.
  • Self-extracting archives open. A .exe with a RAR payload behind the stub is read as the archive it is.
  • Pick single files out of it. --exact (and ticking rows in the app) extracts exactly the entries you name, rather than everything whose path happens to contain the text.

Ziplark drives libunrar's C API directly — see formats/rar/raw.rs for why the wrapper crates were not enough (multi-volume reads out of bounds there, a failed entry throws away the archive handle, and the struct layouts do not match the library's packed headers, which silently mis-reads every field past file_attr).

Why Ziplark

  • Small. Size-optimized release profile (opt-level=z, LTO, stripped, panic=abort). The desktop app uses the OS webview (no bundled Chromium).
  • Faithful. Permissions, modification times and symlinks survive the round trip, so an extracted binary still runs and an extracted tree still looks like the one you archived.
  • Safe. Every extraction path is funneled through a single guard, and it checks both ways out: the entry name (../, absolute paths) *and* what is actually on disk, so a symlink — planted by an earlier entry of the same archive or sitting in the destination already — can't be used to redirect a write. No entry can escape the destination directory.
  • One engine. The GUI, CLI and MCP server are thin shells over ziplark-core; whatever the CLI does, the app does identically.

Repository layout

crates/ziplark-core   the archive engine (all formats, the security guard)

crates/ziplark-cli the ziplark command-line tool crates/ziplark-mcp the MCP server (drive Ziplark from any LLM) src-tauri the Tauri 2 desktop app (Rust commands) ui the desktop frontend (vanilla HTML/CSS/JS)

1. Desktop app

# dev run (opens the window)

cargo tauri dev # or: cargo run -p ziplark-gui

build a release .app + .dmg (macOS), .exe/.msi (Windows), AppImage/deb (Linux)

cargo tauri build

Drag an archive onto the window to inspect & extract it, or switch to **Create**

to drag in files/folders, pick a format + compression level (and optional password), and save.

2. CLI — ziplark

cargo build --release -p ziplark-cli      # binary at target/release/ziplark

ziplark list movie.rar ziplark cat repo.tar.gz src/main.rs ziplark grep "TODO" repo.tar.gz -i --include "*.rs" ziplark diff v1.zip v2.tar.zst -u ziplark hash release.pkg --algo sha256 ziplark extract photos.zip -o ./out --smart ziplark create backup.tar.zst ./src ./README.md --level best --split 100M ziplark add backup.tar.zst ./CHANGELOG.md ziplark mv backup.tar.zst CHANGELOG.md docs/CHANGELOG.md ziplark rm backup.tar.zst docs/CHANGELOG.md --exact ziplark convert legacy.rar clean.tar.zst --level best ziplark create secret.zip ./private --password hunter2 ziplark test download.7z ziplark info mystery.bin

Every command takes `--json` for scripting. `--include <PAT>` filters entries on

extract; --smart avoids tarbombs and double-nesting; --level store|fast|default|best and --password apply to create/add.

Right-click (file-manager) integration

Add Extract here with Ziplark and Compress to ZIP with Ziplark to your OS file manager's context menu:

ziplark shell-integration install      # enable

ziplark shell-integration status # show what's installed ziplark shell-integration uninstall # remove

Per platform: macOS installs two Automator Quick Actions (Finder → right-click → Quick Actions); Windows adds per-user (HKCU, no admin) shell verbs on archive file types and on files/folders; Linux installs KDE service menus and Nautilus scripts. Every entry just calls the ziplark CLI (extract-here / compress-zip), so it follows wherever the binary lives. Both helper commands are also usable directly:

ziplark extract-here movie.zip         # → ./movie/ next to the archive

ziplark compress-zip ./photos ./a.txt # → ./Archive.zip next to them

3. MCP server — ziplark-mcp

A Model Context Protocol server (JSON-RPC over stdio). Read tools (ziplark_info, ziplark_list, ziplark_read, ziplark_grep, ziplark_diff, ziplark_hash, ziplark_test) are always available; the write tools (ziplark_extract, ziplark_create, ziplark_add, ziplark_rename, ziplark_remove, ziplark_convert) require --allow-write.

cargo build --release -p ziplark-mcp

Or install the MCP Bundle — ziplark-mcp- .mcpb on the releases page, one file carrying the server for macOS, Windows and Linux. Ziplark is listed in the official MCP registry as io.github.zhitongblog/ziplark, so clients that read the registry can find it on their own.

Register it with an MCP client:

{

"mcpServers": { "ziplark": { "command": "/path/to/target/release/ziplark-mcp", "args": ["--allow-write"] } } }

Big archives don't flood the context

ziplark_list is paged. It returns at most limit entries (default 200) starting at offset, always alongside the archive's true total_entries, so listing a 200 000-entry disc image costs the same as listing a small ZIP:

{ "name": "ziplark_list", "arguments": { "path": "disc.iso", "limit": 200 } }

// -> { "total_entries": 203411, "returned": 200, "next_offset": 200, // "truncated": true, "top_level": [ { "prefix": "usr/share", "entries": 88120 }, … ] }

When the result is truncated it also carries top_level — entry counts grouped by directory, descending past a single root — so a client can see the *shape* of a huge archive without paging through it. To go straight to what you want, filter instead of paging: include takes path patterns, matched as globs when they contain * or ? and as substrings otherwise, and applies before paging. dirs selects only files or only directories.

{ "name": "ziplark_list",

"arguments": { "path": "disc.iso", "include": ["*/etc/*.conf"], "dirs": false } }

Building & testing

cargo test                 # engine round-trip + security tests

cargo build --release # all crates, size-optimized

License

MIT © 2026 doaipm — a doaipm.com project. See LICENSE.

Ziplark bundles third-party open-source components under their own licenses, acknowledged in THIRD_PARTY_LICENSES.md. Note in particular that RAR extraction uses the UnRAR library, which is under the UnRAR license (not MIT) and may not be used to re-create the RAR compression algorithm.