In-depth architectural comparison of the Live Translate MCP and Kaeris MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Live Translate MCP
Translation Services · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Kaeris MCP
Translation Services · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Live Translate MCP if you need specialized Translation Services tools running via a local process. Choose Kaeris MCP if your workspace requires Translation Services integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Live Translate MCP when:
You need dedicated capabilities in the Translation Services domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: ANTHROPIC_API_KEY.
Real-time English ↔ Mandarin Chinese speech translation. Transcribes audio locally with Whisper, translates via Claude API, and synthesises speech locally with Piper TTS. Pass a WAV file path and Claude handles the rest.
AI localization: translate an app's string files into 46 languages (JSON, .arb, .po, .strings, Android XML, …) with placeholder-safe, reproducible output — from Claude/Cursor.
Category & Scope
Tools & Capabilities Breakdown
Live Translate MCP Tools (3)
translate_file
Translate a WAV audio file. Pass an absolute path — the server transcribes it, translates the text via Claude, synthesises speech, saves `<name>_translated.wav` next to the original, and plays it automatically.
translate_speech
Translate raw audio passed as a base64-encoded WAV string. Returns the transcription, translation, and synthesised audio as base64 WAV — useful for programmatic workflows.
health_check
Verify that all dependencies (Whisper model cache, Piper voice files, `espeak-ng`) are present and ready before making a translation request.
Kaeris MCP Tools (7)
kaeris_scan_repo
Discover a repo's i18n setup: locale files found, base language, target languages, framework guess (i18next/next-intl/vue-i18n/Flutter/Android/iOS/gettext/generic)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Live Translate MCP is categorized under Translation Services and uses a local stdio subprocess. In contrast, Kaeris MCP belongs to Translation Services using local stdio subprocess. Select Live Translate MCP when you need capabilities focused on translation services and Kaeris MCP when you require tools for translation services.
Completeness/health per target locale — missing keys, extra keys, placeholder mismatches, plus the quality detectors that gate a merge in CI: number drift, lost inline tags, broken entities/escapes, ICU/CLDR plural gaps (same verdict as `kaeris check --json`)
kaeris_list_missing_keys
The exact missing/broken keys (with source text) for one target locale, so an agent knows exactly what to fix
kaeris_list_languages
List all supported target languages
kaeris_translate
Translate inline strings → per-language results, with QA (placeholder-loss & UI-overflow flags; `verify=True` back-translates to check meaning)
kaeris_translate_file
Translate a file on disk (JSON/YAML/.strings/.po/ARB/XML/CSV/XLIFF/.properties/.resx/.ftl), optional incremental — reproducible via `kaeris.lock
kaeris_add_language
Bootstrap a brand-new target locale by translating the whole source file into it