Ziplark

MCP其他

提供方 zhitongblog

其他 未标注 OAuth 授权 社区 / 第三方 CursorCodexZed
查看接入方式

Free, fast, cross-platform archiver — extracts ZIP/RAR/7z/tar, creates ZIP/7z/tar. Desktop app + CLI + MCP.

一句话选型结论

按资料字段整理

Ziplark 属于其他类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Cursor、Codex、Zed,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

archive compression rust cli file

支持客户端

适用场景

archivecompressionrust

安装与配置

未标注 OAuth 授权
上游未给出传输方式
/path/to/target/release/ziplark-mcp --allow-write

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Ziplark当前 未标注 未标注 未标注 有 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方zhitongblog上游标注的维护方 zhitongblog
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · html本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.8 KB
来自项目仓库与上游目录的原文,未做删改

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 · Report a bug

Install```bash

macOS — Homebrew

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

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 | Create | Encryption |
|---|:---:|:---:|---|
| ZIP | ✅ | ✅ | AES-256 (read ZipCrypto) |
| 7z | ✅ | ✅ | AES-256 |
| RAR / RAR5 (incl. multi-volume, SFX) | ✅ | — | reads encrypted, incl. encrypted headers |
| tar | ✅ | ✅ | — |
| tar.gz / .bz2 / .xz / .zst / .lz4 | ✅ | ✅ | — |
| gz / bz2 / xz / zst / lz4 (single stream) | ✅ | ✅ | — |
| ISO 9660 / Joliet (disc image) | ✅ | — | — |

> RAR and ISO are extract-only: RAR's compression format is proprietary, and ISO
> is a disc-image container (we read ISO 9660 + Joliet with our own dependency-free
> parser). Everything else can be created as well as read.

## 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```bash

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````bash
cargo build --release -p ziplark-cli      # binary at target/release/ziplark

ziplark list  movie.rar
ziplark extract photos.zip -o ./out
ziplark create backup.tar.zst ./src ./README.md --level best
ziplark create secret.zip ./private --password hunter2
ziplark test  download.7z
ziplark info  mystery.bin

Every command takes --json for scripting. --include filters entries on
extract; --level store · fast · default · best and --password apply to create.

Right-click (file-manager) integration

Add Extract here with Ziplark and Compress to ZIP with Ziplark to your
OS file manager's context menu:```bash
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:```bash
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_test) are always available; the write tools
(ziplark_extract, ziplark_create) require --allow-write.```bash
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:```json
{
  "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:```jsonc
{ "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.```jsonc
{ "name": "ziplark_list",
  "arguments": { "path": "disc.iso", "include": ["*/etc/*.conf"], "dirs": false } }

Building & testing```bash

cargo test # engine round-trip + security tests
cargo build --release # all crates, size-optimized
```

License

MIT © 2026 doaipm — a doaipm 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.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Ziplark 怎么安装?

在客户端按下面的安装命令接入:/path/to/target/release/ziplark-mcp --allow-write。装完在客户端配置里引用同一个包或端点。

Ziplark 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Ziplark 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Ziplark 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Ziplark 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Ziplark 能提供哪些能力?

资料显示能力标签包括 archive、compression、rust、cli、file。具体工具清单以官方文档为准。

Ziplark 需要什么运行环境?

运行时为 html。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。