Weblate MCP vs Kaeris MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Weblate MCP vs Kaeris MCP
In-depth architectural comparison of the Weblate 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
Weblate MCP
Translation Services · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Kaeris MCP
Translation Services · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Weblate 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 Weblate 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 (Free / Open Source).
You have access to required keys: WEBLATE_API_URL, WEBLATE_API_TOKEN.
Primary tools included: Weblate REST API access through MCP, Project and component management, Filtered translation search.
Comprehensive Model Context Protocol server for Weblate translation management, enabling AI assistants to perform translation tasks, project management, and content discovery with smart format transformations.
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
Weblate MCP Tools (6)
Weblate REST API access through MCP
Project and component management
Filtered translation search
Single and bulk translation updates
Translation and contribution statistics
Change-history queries
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).
Weblate 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 Weblate 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