Skip to main content
Glama

kaeru

Verified conversions — every one actually run, not just claimed. Your files are never uploaded to convert them. One tool your AI agents and you both use.

kaeru converting a confidential .docx to Markdown, entirely on the local machine

A contract that cannot leave the building, turned into something an agent can read. Note the Tool and Command lines: that is the binary on your machine, and the exact command it ran. Nothing to take on faith.

npx @noguchilin/kaeru --doctor     # what can this machine convert?

Verified, not claimed

Every conversion listed below was actually run, one by one, on real machines — and the output was re-opened with a second tool to prove it isn't empty. The test suite ships with the code, so you can re-run the count yourself.

OS

Conversions offered

Actually passed

Tools installed

macOS 26

4,779

4,753 / 4,753

all

Windows 11

4,062

3,708 / 3,952

ImageMagick, pandoc

Debian (Linux)

3,426

3,218 / 3,329

ImageMagick, pandoc

The macOS row was re-run on 2026-08-25. The Windows and Debian rows are from 2026-08-18 on real machines that did not have poppler installed, so they predate pdf>txt — install poppler there and each gains one more.

npm test        # re-run every combination on your machine
npm run list    # print the conversion table (this is what the numbers count)

Numbers differ per machine on purpose — see below.

Related MCP server: File Convert MCP Server

The table adapts to your machine

kaeru doesn't bundle converters. It finds the ones you already have — and asks each one what its version actually supports. A conversion that can't work is never offered.

$ npx @noguchilin/kaeru --doctor
This machine can do: 4,062 conversions

Tools:
  ✓ magick      C:\Program Files\ImageMagick-7.1.2-Q16-HDRI\magick.EXE
  ✗ ffmpeg      not found
  ...

Install these to unlock more:
  ffmpeg      +468 conversions   winget install Gyan.FFmpeg

Nothing installed? Nothing breaks — you get 0 conversions and a list of one-line installs.

Three doors, one engine

Door

For

Start it

Command line

you, right now

npx @noguchilin/kaeru photo.png --to jpg

MCP server

your AI agents

add one line to .mcp.json

Local web page

you, with a file picker

npm run uihttp://127.0.0.1:19921

All three call the same code, so an agent and a human can never disagree about what's possible. An option that would do nothing is refused rather than ignored — --max on docx>pdf comes back with what that conversion does accept — and the web page only shows a field once the engine says the chosen target accepts it.

For agents (MCP)

{ "mcpServers": { "kaeru": { "command": "npx", "args": ["-y", "@noguchilin/kaeru"] } } }

One tool, convert. Ask for something impossible and it replies with what is possible from that input — or which tool to install.

For humans, from the shell

npx @noguchilin/kaeru photo.png --to jpg
npx @noguchilin/kaeru report.pdf --to pdf --output smaller.pdf   # same format = compress
npx @noguchilin/kaeru a.pdf b.pdf --to pdf --output merged.pdf   # PDFs merge
npx @noguchilin/kaeru contract.pdf --to txt                      # text out of a PDF
npx @noguchilin/kaeru a.png b.png --to png --output tall.png     # images stack
npx @noguchilin/kaeru a.png b.png c.png d.png --to png --columns 2 --output grid.png
npx @noguchilin/kaeru shot.png --to png --max 800 --output small.png  # longest side ≤ 800

It prints the path it wrote and exits. Run it with no arguments and it becomes the MCP server instead — that is how your agent starts it.

For humans, from a page

npm run ui opens a single page on 127.0.0.1 only. Drop a file, pick a target, save the result. It does not stay running — Ctrl-C and it's gone. No Docker, no daemon, no account.

What it converts

Images · video · audio · documents (md, html, tex, docx, odt, epub, and ~30 more) · Office and spreadsheets · PDF · 3D models · Parquet.

PDFs can be merged, split, compressed, rasterised, and read as text. Images, audio and PDFs can be shrunk without changing format. --max N bounds an image's longest side — it only ever shrinks, so a small image is returned untouched rather than blown up. Pass several images and they are joined into one (--columns sets how many per row). Pass a URL to pull from video sites.

A scanned PDF has no text to give. --to txt on one does not hand you an empty file and call it a conversion — it tells you the pages are images, and points you at --to png. That is the same rule as the headline: a result you can't verify isn't offered.

CJK encodings are detected automatically (a Shift_JIS CSV from Excel just works).

Every result comes with its receipt

Converted: csv>xlsx
Output:    /path/to/data.xlsx
Tool:      soffice
Command:   soffice --headless --convert-to xlsx --outdir /tmp/... /path/to/data.csv
Took:      3,512 ms

You can always see which program touched your file, and repeat it by hand.

Install the converters

kaeru calls these; install the ones you need (or none, and add them later).

brew install imagemagick ffmpeg pandoc weasyprint qpdf poppler img2pdf yt-dlp assimp duckdb ghostscript
brew install --cask libreoffice
winget install ImageMagick.ImageMagick Gyan.FFmpeg JohnMacFarlane.Pandoc QPDF.QPDF `
  oschwartz10612.Poppler yt-dlp.yt-dlp Assimp.Assimp DuckDB.cli `
  ArtifexSoftware.GhostScript TheDocumentFoundation.LibreOffice
pip install weasyprint img2pdf
sudo apt install imagemagick ffmpeg pandoc qpdf poppler-utils img2pdf yt-dlp assimp-utils ghostscript libreoffice
pip install weasyprint

Privacy and security

  • Files are processed by local programs. kaeru makes no network requests (except when you explicitly pass a video-site URL — that path downloads, by definition).

  • What kaeru does not control: what you do with the result. If your agent then reads the converted file, its contents go to whatever model provider that agent uses. kaeru governs the conversion, not the reading. For a file that must never reach a model, convert it and open it yourself in the local web page (npm run ui) instead of handing it to an agent.

  • The web page binds to 127.0.0.1, rejects non-localhost Host headers, and hands results back by an unguessable id.

  • Existing files are never overwritten unless you ask for it.

  • No telemetry. Ever. Not anonymous, not opt-out — none.

Three independent models reviewed the source on 2026-08-18; every exploitable finding was fixed the same day. One known risk is not fixed: converting untrusted HTML or SVG can embed local files in the output. Details, severities and mitigations: SECURITY.md.

Tests

Command

What it checks

npm test

every listed conversion actually runs, output re-opens

node test/quality.mjs

images round-trip pixel-for-pixel; text survives

node test/fidelity.mjs

documents keep headings, tables, lists, emphasis

node test/languages.mjs

12 writing systems keep their characters

node test/platforms.mjs

tool lookup is correct for macOS / Windows / Linux

Known gaps are written down, not hidden — see docs/.

Support

Issues are welcome. This is a one-person project: no response time is promised. For a bundled installer or a support contract, see the bottom of this file.

License

MIT. The converters it calls have their own licenses.


Need this installed for a team, or with a support contract? Open an issue titled commercial and I'll get back to you.

Available Tools

1 tool
convertA

ファイルを別の形式に変換する(0通り・入力0形式)。変換はこの端末の中で行い、変換のためにファイルをどこへも送らない(動画サイトの URL を渡した時だけ、その取り込みで通信する)。扱うもの: 画像・動画・音声・文書(md/html/tex/docx/odt/epub ほか)・Office と表計算(CSV の文字コードは自動判別)・PDF・3Dモデル・Parquet。PDF は結合(input に複数)・切り出し(pages)・圧縮・画像化・文字の取り出し(to: txt)ができる。絵も複数渡すと1枚にまとまる(columns で横に並べる数を決める)。max で長い方の辺を画素数で収められる(縮小のみ)。同じ形式を to に指定すると、形は変えずに小さくする(画像・音声・PDF)。動画サイト(YouTube・X 等)は input に URL を渡す。対応していない組み合わせを頼むと、その入力から作れる形式の一覧が返る。出力先に既にファイルがある時は止まる(消してよいなら overwrite: true)。

ParametersJSON Schema
NameRequiredDescriptionDefault
toYes出力形式(拡張子。例: pdf)
maxNo絵の長い方の辺を、この画素数に収める(縮小のみ。元より大きくはしない)
inputYes入力ファイルの絶対パス。動画サイトの URL でもよい。PDF の結合だけ複数渡せる
pagesNoPDF から切り出すページ(例: 1-3,5)。指定しなければ全ページ
outputNo出力先の絶対パス。省略時は入力と同じ場所に置く
columnsNo絵を複数まとめる時の横に並べる数。既定は 1(縦に積む)
overwriteNo出力先に既にファイルがある時、上書きしてよいか。既定は false(黙って消さない)

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully carries the behavioral burden and does so impressively: it discloses that conversion happens locally, the only network communication is when a video-site URL is passed, overwriting requires explicit opt-in, and unsupported requests return a format list. It also clarifies that max only shrinks and same-format output means size reduction, which prevents agent misexpectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense and front-loaded with the core purpose and local-processing guarantee. It is written as one long paragraph, and the garbled '0通り・入力0形式' phrase is a readability defect, but every substantive sentence earns its place and no content is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a highly polymorphic tool with 7 parameters and no output schema, the description covers formats, operations, constraints, network behavior, overwrite safety, and error-response behavior. Nothing critical for invoking the tool correctly is missing; it even handles edge cases like same-format compression and unsupported requests.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning beyond every parameter: input can be a URL or multiple files for PDF merge; to can be the same format to compress; max is shrink-only; columns has a default of stacking vertically; pages defaults to all pages; overwrite defaults to false to avoid silent deletion. This is excellent value-add over the raw JSON schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the resource ('file') and the action ('convert to another format'), and it enumerates supported categories (image, video, audio, document, PDF, etc.). However, the opening parenthetical '0通り・入力0形式' is nonsensical and slightly undermines clarity, and the broad scope means it cannot be sharply distinguished from some conceivable conversion sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete usage guidance for several scenarios: PDF merging requires multiple inputs, pages extracts ranges, columns controls the grid, max shrinks only, and same-format to compresses. It also says unsupported combinations return a list of possible formats. There are no sibling tools to compare against, so it cannot give explicit when-not-to-use alternatives, which keeps it just below 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.10.2
    • First observedconvert

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

ツールが convert のみで、他のツールと混同する余地がまったくない。単一ツールのためエージェントが選択を誤る可能性はない。

Naming Consistency5/5

ツール名が convert という明確な動詞で統一されており、命名の不整合や混在が存在しない。単一ツールでも分かりやすい命名と言える。

Tool Count4/5

ツールは1つだけだが、ファイル変換というサーバーの目的に対して convert が広範な形式と操作をカバーしており、実用上は十分に機能する。数は少ないが、無意味に分割せず1つに集約した設計は妥当。

Completeness5/5

画像・動画・音声・文書・PDF・3Dモデル・Parquet など主要な変換対象を網羅し、PDF結合や画像連結、動画URL取り込み、上書き制御などの必要な操作も備えている。変換ドメインにおける大きな欠落は見当たらない。

Maintenance

ActivityMaintained
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers