MooTool is a multi-platform desktop developer toolbox application (a 'Swiss army knife' for developers) providing roughly 25 utility tools: JSON formatting/validation/JSONPath inspection, text diff, regex testing, cron expression building, encoding/decoding, crypto, QR code generation/decoding, an HTTP client, host file editor, environment variable sessions, translation, network diagnostics, color picker, image processing, PDF merge/split, system hardware info, calculator, and time conversion. The repository is a monorepo containing six parallel frontend implementations of the same product family: a legacy Java Swing app (src/main/java, the current stable 1.8.7 release), an Electron/React app (next/), a Tauri/Rust+React app (next-tauri/), a Kotlin JetBrains Compose Desktop app (next-compose/), an experimental macOS native SwiftUI app (next-macos-native/ plus macos/), and a partial JavaFX variant (next-fx/), plus an early Flutter runner. The Electron, Tauri, and Compose lines are the actively developed 'next' product; heavy legacy-migration machinery (LegacyToolIdMapper, LegacySqliteParsers, ElectronNextSettingsImport) shows the Swing edition being phased out. The most distinctive subsystem is the git-backed vault: a file store for JSON documents and quick notes with automatic checkpoint commits on idle, external-change monitoring, merge/rebase conflict detection with a unified diff preview and reload/save-copy/keep resolution flow, and remote management. The app also ships a Model Context Protocol (MCP) server over stdio exposing tools such as mootool_json_format, mootool_encode, mootool_timestamp, mootool_diff, and mootool_json_query, bridging the desktop utilities to AI coding agents (Claude Code, Cursor, Codex). Other notable infrastructure includes offline OCR via ONNX Runtime child processes with network access disabled, an update coordinator with SHA-512-verified atomic downloads, SQLite-backed session/history persistence, i18n catalogs for zh-CN/en-US/ja-JP, and screen-capture/color-picker OS integrations. Engineering character: the Compose codebase consistently separates pure domain engines (CronEngine, DiffEngine, VaultConflictEngine, RegexEngine, etc.) from *WiringPresentation UI-guard objects, making core logic unit-testable without UI frameworks; test suites are extensive (hundreds of tests across Vitest, JUnit, Kotlin test, Playwright, and Compose UI capture tests). The weaknesses are architectural: identical features are reimplemented in Java, TypeScript, Kotlin, Rust, and Swift with subtle behavioral drift (e.g., cron DST handling differs between Electron and Compose), visual capture tests assert exact pixel colors and are environment-brittle, and the legacy Swing codebase retains dead/commented modules. This is an application-dominant repository with no research character; the SQLite usage is application persistence, not analytics.