In-depth architectural comparison of the MachineTranslation.com 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
MachineTranslation.com MCP
Translation Services · Remote HTTP/SSE
Quality: 64/100 (Good) | Auth: OAuth 2.0
Kaeris MCP
Translation Services · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose MachineTranslation.com MCP if you need specialized Translation Services tools running via a hosted cloud SSE transport. 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 MachineTranslation.com MCP when:
You need dedicated capabilities in the Translation Services domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Paid Service).
Primary tools included: SMART translation across 22 AI models, Consensus-based translation output, Supported language code discovery.
Brings SMART consensus translation into any MCP client. Runs your text through 22 leading AI translation models at once and returns only the output the models agree on, so you get a confidence-backed result instead of a single engine's guess. Exposes two tools: smart_translate (text, source language, target language) and list_languages (all supported language codes). Hosted remote server at https://www.machinetranslation.com/mcp over streamable HTTP — no install, no API key, just connect the URL and sign in. Built for translators, localization and content teams, marketers, and developers.
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.
Tools & Capabilities Breakdown
MachineTranslation.com MCP Tools (6)
SMART translation across 22 AI models
Consensus-based translation output
Supported language code discovery
Hosted streamable HTTP MCP endpoint
OAuth 2.1 connector authentication
Optional personal access token support for developer clients
Kaeris MCP Tools (7)
kaeris_scan_repo
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).
MachineTranslation.com MCP is categorized under Translation Services and uses a remote streaming HTTP/SSE transport. In contrast, Kaeris MCP belongs to Translation Services using local stdio subprocess. Select MachineTranslation.com MCP when you need capabilities focused on translation services and Kaeris MCP when you require tools for translation services.
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)
kaeris_status
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