Mochify CLI C3bf885f

MCP设计创作

提供方 getmochify

设计创作 未标注 会话登录 社区 / 第三方 Claude DesktopClaude

一个基于命令行的图像压缩和转换工具,支持多种现代图像格式(如AVIF、JXL、WebP、Jpegli),并提供MCP服务器功能以便AI助手直接访问图像处理服务。

一句话选型结论

按资料字段整理

Mochify CLI C3bf885f 属于设计创作类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

图像处理Rust本地部署命令行工具格式转换AI集成隐私保护

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后客户端会列出约 1 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
出图与素材

生成配图、图标与素材。

设计稿处理

读取设计稿、批量改尺寸或导出。

内容生成

按主题生成文案与视觉草稿。

选择建议

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

值得选的地方

  • 资料标注 1 个工具,职责相对集中,接入后不容易误操作。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Mochify CLI C3bf885f当前 1 未标注 未标注 无 2026-05-17
Cursor Talk To Figma MCP Da1c7911 40 未标注 未标注 无 2026-05-17
Blender MCP 17 stdio · 本地进程 本地部署 有 2026-05-18
Nova Canvas MCP Server 2 stdio · 本地进程 本地部署 有 2026-05-17
Figma Context MCP 3aaa8d28 未标注 未标注 支持远程部署 无 2026-05-17
kreuzberg 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

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

详细介绍

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

mochify-cli

A command-line tool and MCP server for mochify.app — a fast, privacy-first image compression and conversion API powered by a native C++ engine.

Compress and convert images to modern formats (AVIF, JXL, WebP, Jpegli) from your terminal, work on PDFs, or give AI assistants like Claude direct access to the same engine over the Model Context Protocol — either as a local stdio server (mochify serve) or the hosted one at mcp.mochify.app, which needs no install at all.

Installation

macOS (Homebrew):```bash
brew tap getmochify/mochify
brew install mochify


**Windows (Scoop):**```powershell
scoop bucket add mochify https://github.com/getmochify/scoop-mochify
scoop install mochify

Linux / WSL:```bash

x86_64

curl -L https://github.com/getmochify/mochify-cli/releases/latest/download/mochify-linux-x86_64 -o mochify
chmod +x mochify
sudo mv mochify /usr/local/bin/

arm64

curl -L https://github.com/getmochify/mochify-cli/releases/latest/download/mochify-linux-arm64 -o mochify
chmod +x mochify
sudo mv mochify /usr/local/bin/


**Cargo (all platforms):**```bash
cargo install mochify

Requires Rust. Easiest option on Linux/WSL if you already have the toolchain.

Manual: All binaries at Releases.

From source:```bash
cargo install --path .


## Authentication

Sign in with your mochify.app account to unlock your full quota:```bash
mochify auth login

This opens your browser, where you sign in and authorize the CLI. Credentials are saved automatically to ~/.config/mochify/credentials.toml — no environment variables or manual key copying required. Both the CLI and MCP server pick them up automatically.

On a machine without a browser (over SSH, say), sign in with a code instead — open the link it prints on any device and type the code:```bash
mochify auth login --no-browser
``````bash
mochify auth status # check whether you're signed in
mochify auth logout # remove saved credentials


Without an account you get 3 images per batch (IP-based). With a free account: 25 images/month. Sign up at mochify.app.

## CLI Usage```bash
mochify [OPTIONS] <FILES>...

Options

Flag Description
-t, --type Output format: jpg, png, webp, avif, jxl
-w, --width Target width in pixels
-H, --height Target height in pixels
--crop Crop to exact dimensions (saliency-guided)
--region Crop to a rectangle, as fractions 0–1 of the upright image from the top-left
--redact Hide areas: faces and/or ;-separated boxes x,y,w,h (same convention as --region)
--redact-style fill (solid black, default) or blur (cosmetic only)
-r, --rotation Rotation: 0, 90, 180, 270
-o, --output Output directory (default: same as input)
-n, --name Base name for the output file (without extension)
--clarity Apply clarity (midtone contrast enhancement — crisper, more detailed look)
--remove-bg Remove the background (AI foreground isolation)
--background Composite colour for --remove-bg (white, #ff0000, …)
--keep-metadata Preserve EXIF/metadata (stripped by default)
-q, --quality Output quality 1–100 (default: automatic)
--smart-compress Saliency-guided quality — detail keeps more, flat areas less
--brightness Exposure, -100 (darkest) to +100 (brightest)
--optimize-for-web Progressive + 4:2:0 chroma — smallest file to serve
--lossless Pixel-exact output (jxl, webp, png only)
--hdr [MODE] Ultra HDR gain map: preserve (bare flag) or generate
-p, --prompt Natural-language prompt — resolves all params automatically
-j, --jobs Files to process at once (default 4; 1 for strictly one at a time)
-k, --api-key API key override (or set MOCHIFY_API_KEY env var)

Examples```bash

Convert to AVIF

mochify photo.jpg -t avif

Resize and convert to WebP

mochify photo.jpg -t webp -w 800

Batch convert a folder to AVIF at 1200px wide

mochify ./images/*.jpg -t avif -w 1200 -o ./compressed

Natural-language prompt — let the AI pick the right params

mochify photo.jpg -p "convert to avif, 1200px wide"
mochify photo.jpg -p "optimise for eBay"
mochify photo.jpg -p "remove background and convert to WebP"
mochify photo.jpg -p "resize to 50%, strip EXIF, keep as WebP"

Custom output name

mochify photo.jpg -t webp -n hero
mochify product.jpg -p "optimise for Shopify" -n product-main

Pipe file paths from stdin

find . -name ".jpg" | mochify -t webp -o ./out
cat images.txt | mochify -p "convert to avif 1200px wide" -o ./compressed
ls
.heic | mochify -t jpg


### Quality

Quality is chosen automatically unless you say otherwise.```bash
# Fixed quality
mochify photo.jpg -t webp -q 70

# Let saliency pick it — detailed subjects keep more, flat areas less
mochify photo.jpg -t avif --smart-compress

# Smallest file to serve from a web server
mochify photo.jpg -t webp --optimize-for-web

# Brighten a dark photo
mochify photo.jpg --brightness 30

# Pixel-exact
mochify scan.png -t webp --lossless

--lossless only works for jxl, webp and png — jpg and avif are rejected before the request goes out. It overrides -q and --smart-compress, and the output is usually larger than the input: lossless preserves pixels, not file size. A source that is already lossy (JPEG, AVIF, HEIC) comes back as the best lossy encode instead, since nothing can restore what that file discarded — the CLI says so when that happens.

Cropping to a region

--crop finds the subject itself. --region is for when you — or the AI assistant driving the MCP server — already know which part of the picture you want:```bash

The bottom-left quarter

mochify photo.jpg --region 0,0.5,0.5,0.5

A region, then sized: -w/-H apply to the cropped part

mochify photo.jpg --region 0.2,0.1,0.6,0.8 -w 800 -t webp


The four numbers are `x,y,width,height` as **fractions** of the image (0 to 1), measured from the top-left of the picture as it displays — the right way up, even for a phone photo stored sideways. Fractions rather than pixels so the same box works whatever size the image is viewed at. A value above 1 is refused before the request goes out, since that is almost always a box in pixels. The region is cut first: `-w`/`-H`, `--crop`, `--rotation` and `--remove-bg` all act on it. `--verbose` prints the pixel rectangle that was actually cut.

Over MCP this is how an assistant can crop to *content* — "crop to the feet", "just the logo": it looks at the image itself, picks the box, and Mochify only ever receives the four numbers.

### Redaction

Hide faces, number plates, addresses or anything else before an image goes anywhere:```bash
# Every face, found automatically
mochify family.jpg --redact faces

# A number plate, as a box (fractions of the upright image, like --region)
mochify car.jpg --redact 0.38,0.71,0.24,0.08

# Both, softened with a blur instead of a solid fill
mochify street.jpg --redact "faces;0.38,0.71,0.24,0.08" --redact-style blur

Separate entries with ; — the , belongs to the box. fill (solid black) is the default and the one to use for anything that must stay secret; blur is for the look of a blurred face, and blurred text or faces can sometimes be recovered.

Redaction always strips metadata (EXIF can hold a thumbnail of the original) and removes any HDR gain map (which holds the scene's structure), even if you asked to keep them. faces is best-effort — it can miss small faces and side profiles — so the CLI says when it found none. Check the output before sharing it.

HDR (Ultra HDR gain maps)

--hdr controls the Ultra HDR / ISO 21496-1 gain map that makes a photo render with real headroom on an HDR display.

Mode What it does
--hdr (or --hdr preserve) Keeps a gain map the source already has. Never invents one, so it does nothing to an SDR photo.
--hdr generate Keeps an existing gain map and synthesises one when the source is plain SDR. This is the one for "make it HDR".

Only jpg output can carry a gain map (jxl carries HDR by a different route; avif, webp and png cannot), so pair it with -t jpg. It is also skipped alongside --clarity or --remove-bg, which change the base the gain map is a ratio to. The CLI reads the X-Mochify-HDR response header and tells you when the output ended up with no gain map.```bash

Keep the headroom an iPhone photo already captured, converting to JPEG

mochify IMG_1234.heic -t jpg --hdr

Give an SDR photo a gain map

mochify photo.jpg --hdr generate

Or just say so

mochify photo.jpg -p "make this HDR"


### Output file naming

By default, when the output format and directory match the input, the result is saved as `{name}_mochified.{ext}` so it's always clear something happened. If that file already exists, a numeric suffix is added (`_1`, `_2`, etc.). When the format changes (e.g. `.jpg` → `.webp`), the extension change is already unambiguous so no suffix is added.

Use `-n, --name` to set an explicit base name: `mochify photo.jpg -t webp -n hero` saves `hero.webp`. The prompt path also supports this: `mochify *.jpg -p "optimise for Shopify, name them product"` will produce `product.webp`, `product_1.webp`, etc.

### PDF processing

PDFs are detected automatically by the `.pdf` extension, and `--op` picks what to do with them. (PDFs and images can't be mixed in a single command — run them separately.)

`create` is the exception: its inputs are images, so there is nothing in a `.jpg` to route on. Pass `--op create`, or just say "pdf" in a prompt — `mochify *.jpg -p "convert to pdf"` builds one too.

| Op | Takes | Returns | What it does |
|---|---|---|---|
| `optimize` | a PDF | `.pdf` | Recompresses the images inside the PDF. Text, fonts, vector art and layout are untouched, so the document stays searchable. |
| `extract` | a PDF | `.zip` | Pulls out the images somebody placed into the document, at the resolution they were stored at. |
| `rasterize` | a PDF | `.zip` | Renders every page to an image, text and all. |
| `split` | a PDF | `.zip` | Explodes the PDF into one single-page PDF per page. |
| `create` | images | `.pdf` | Builds a PDF from images, one page per image, in the order given. |

| Flag | Applies to | Description |
|---|---|---|
| `--op ` | all | `optimize`, `extract`, `rasterize`, `split`, `create` |
| `-t, --type ` | rasterize, extract | `png`, `jpg`, `webp`, `avif`, `jxl` — plus `original` for `extract` (no re-encode) |
| `--dpi ` | rasterize, optimize, create | Render resolution (rasterize, default `150`), target resolution for the images kept inside the PDF (optimize), or page sizing (create) |
| `-q, --quality ` | all but split | Output quality `1–100` (same flag as for images) |
| `--max-width ` | extract, optimize, create | Cap image width in pixels; `0` leaves sizes alone |
| `--min-size ` | extract, optimize | Skip images smaller than this on either axis; `0` takes everything |
| `--page ` | create | `fit` (default), `a4`, `letter` |
| `--no-combine` | create | One single-page PDF per image, returned as a `.zip` |
```bash
# Make a PDF smaller without touching the text
mochify report.pdf --op optimize -q 75 --dpi 150

# Pull the embedded images out as WebP, capped at 1600px
mochify brochure.pdf --op extract -t webp --max-width 1600

# Render pages to PNG at 150 DPI, or high-res JPEGs for print
mochify document.pdf --op rasterize -t png --dpi 150
mochify document.pdf --op rasterize -t jpg --dpi 300 -q 90

# One PDF per page
mochify document.pdf --op split

# Build a PDF from images (one page per image, in the order given)
mochify page-*.jpg --op create --page a4 -n scanned
mochify page-*.jpg --op create --no-combine   # one PDF per image, as a zip

# Or describe it in natural language
mochify report.pdf -p "compress this pdf"
mochify brochure.pdf -p "get the photos out as png"
mochify document.pdf -p "split into pngs"
mochify page-*.jpg --op create -p "one a4 pdf, good quality"

# A prompt that says "pdf" on image inputs implies --op create
mochify page-*.jpg -p "convert to pdf"
mochify scan-*.png -p "one a4 pdf, good quality"
mochify shot-*.jpg -p "each image as its own pdf"

Outputs are named after the input: report_compressed.pdf, brochure_images.zip, document_rasterized.zip, document_pages.zip, and .pdf for create (override with -n).

optimize, extract, rasterize and split require a paid plan; create works on every plan, including Free.

MCP server

Mochify speaks MCP two ways. Both call the same engine at api.mochify.app, where encoding happens in RAM and the original is discarded immediately. The difference is where your files live.

Hosted (mcp.mochify.app) Local (mochify serve)
Install none this binary
Transport Streamable HTTP stdio
Auth OAuth 2.0 + PKCE, one browser approval mochify auth login, or anonymous
Input public HTTPS URL, or base64 bytes absolute paths on your disk
Output short-lived download URL (~5 min) on files.mochify.app written straight to disk
Image bytes through the agent on base64 input never
Handles images images and PDFs

Reach for hosted when the agent has no filesystem — Claude.ai, a hosted runtime, anything talking to images that already live on the web. Reach for local when the files are on your machine, which is most of the time: nothing but a path and a byte count ever enters the model's context.

Both can run side by side in the same client with independent tokens.

Hosted (no install)

Register https://mcp.mochify.app as a remote MCP connector and complete the OAuth flow once. No API key to copy or rotate.

  • Claude.ai — Settings → Connectors → Add custom connector
  • Claude Desktop — Settings → Connectors, or a "type": "http" entry in the config
  • Cursor, Windsurf, Gemini, any client with remote MCP support — same URL

Or install it from Smithery:

Results come back as a download URL with roughly a five-minute expiry, held in an in-memory pickup store until fetched or the TTL lapses. Originals are never stored. This is the one path that is not zero-retention end to end — see why we relaxed zero retention for MCP.

Local (stdio)

Run mochify auth login first, then point your client at the binary:json { "mcpServers": { "mochify": { "command": "mochify", "args": ["serve"] } } }

Claude Desktop's config lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS. Restart the client afterwards; the server picks up your saved credentials automatically. Any stdio MCP client works the same way — Cursor, Continue, Cline, Claude Code.

Set MOCHIFY_API_KEY instead for CI, or leave auth off entirely to run on the anonymous free tier.

Tools

Both servers expose the same four tools. The difference is how files get in and out: the local server takes paths and writes to disk, the hosted one takes URLs or base64 and hands back a short-lived download URL.

Tool Takes Does
squish one image Everything on the image side: format conversion, resize, crop, rotate, background removal, brightness, clarity, quality control (fixed, saliency-guided or lossless), web optimisation, Ultra HDR gain maps.
pdf one PDF optimize (smaller PDF, text and layout untouched), extract (the images inside it, as a zip), rasterize (pages to images, as a zip), split (one PDF per page, as a zip).
pdf_create images Builds a PDF, one page per image, in the order given. fit, a4 or letter pages; combine: false returns a zip of single-page PDFs.
check_usage nothing Reports operations remaining this billing period and the plan they belong to. Needs authentication.

squish parameters: file_path, type, width, height, crop, rotation, quality, smart_compress, lossless, optimize_for_web, brightness, clarity, remove_background, background, strip_metadata, hdr, output_dir, output_name.

pdf parameters: file_path, op, type, dpi, quality, max_width, min_size, output_dir.

pdf_create parameters: file_paths, page, quality, dpi, max_width, combine, output_name, output_dir.

check_usage takes no parameters.

Every tool reads and writes the filesystem itself, so the agent never has to load an image to process it. Responses carry the saved path plus whatever the API reported: how much smaller the PDF got, whether a gain map survived, whether a lossless request had to fall back to lossy, and how much quota is left.

Usage

Describe what you want in natural language, with the full path to your file:

> "Convert /Users/me/Desktop/photo.jpg to AVIF at 1000px wide"

> "Compress all the JPEGs in /Users/me/projects/blog/images/ to WebP and save to /Users/me/projects/blog/compressed/"

> "Optimise /Users/me/Desktop/product.jpg for eBay"

> "Remove the background from /Users/me/Desktop/shirt.png and save as WebP"

> "Compress /Users/me/Desktop/report.pdf — it's too big to email"

> "Rasterize /Users/me/Desktop/report.pdf to PNGs at 200 DPI"

> "Make /Users/me/Desktop/sunset.jpg HDR"

> "Brighten /Users/me/Desktop/dim.jpg a bit and optimise it for my website"

> "Turn the scans in /Users/me/Desktop/receipts/ into one A4 PDF"

API

Powered by https://api.mochify.app — /v1/squish for images, /v1/pdf for PDF optimize/extract/rasterize/split/create. Files are processed in RAM and never written to disk.

Plan Ops/month Files per batch Max file size
Free (no account) 3 per batch 3 20 MB
Free (with account) 25 3 20 MB
Day Pass ($2 one-time) 100, valid 24h 25 75 MB
Seller ($7.99/mo) 300 25 75 MB
Pro ($24.99/mo) 1,200 25 75 MB
Growth ($79.99/mo) 5,000 25 75 MB

One operation is one output image. Compress, convert, resize and rotate the same file and it stays one operation; ask for two formats at two sizes and that is four. PDF optimize, extract, rasterize and split need a paid plan (Day Pass counts); create works on every plan including Free.

Visit mochify.app for the web interface, pricing, and API docs.

Questions

Ask in GitHub Discussions — answers stay searchable there, which a support email thread does not. Bugs and feature requests belong in Issues. For anything account or billing related, email hello@mochify.app.

Listed in the official MCP Registry as mcp-name: app.mochify/mochify.

常见问题

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

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Mochify CLI C3bf885f 怎么在 Claude Desktop、Claude 里配置?

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

Mochify CLI C3bf885f 收费吗?

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

Mochify CLI C3bf885f 需要 API Key 吗?

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

Mochify CLI C3bf885f 支持哪些客户端?

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

Mochify CLI C3bf885f 能提供哪些能力?

资料显示约 1 个工具;能力标签包括 图像处理、格式转换、Rust、Claude、命令行工具。具体工具清单以官方文档为准。

热门专题

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

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