In-depth architectural comparison of the Weblate MCP and Xcomet MCP Server 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
Xcomet MCP Server
Translation Services · Local stdio
Quality: 60/100 (Good) | Auth: other
Verdict Summary: Choose Weblate MCP if you need specialized Translation Services tools running via a local process. Choose Xcomet MCP Server 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.
Translation quality evaluation using xCOMET models. Provides quality scoring (0-1), error detection with severity levels (minor/major/critical), and optimized batch processing with 25x speedup.
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
Xcomet MCP Server Tools (3)
xcomet_evaluate
Evaluate the quality of a translation using xCOMET model.
This tool analyzes a source text and its translation, providing:
- A quality score between 0 and 1 (higher is better)
- Detected error spans with severity levels (minor/major/critical)
- A human-readable quality summary
Args:
- source (string): Original source text to translate from
- translation (string): Translated text to evaluate
- reference (string, optional): Reference translation for comparison
- source_lang (string, optional): Source language code (ISO 639-1)
- target_lang (string, optional): Target language code (ISO 639-1)
- response_format ('json' | 'markdown'): Output format (default: 'json')
- use_gpu (boolean, optional): Use GPU for inference if available (default: false)
Returns:
For JSON format:
{
"score": number, // Quality score 0-1
"errors": [ // Detected errors
{
"text": string,
"start": number,
"end": number,
"severity": "minor" | "major" | "critical"
}
],
"summary": string // Human-readable summary
}
Examples:
- Evaluate EN→JA translation quality
- Check if MT output needs post-editing
- Compare translation against reference
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, Xcomet MCP Server belongs to Translation Services using local stdio subprocess. Select Weblate MCP when you need capabilities focused on translation services and Xcomet MCP Server when you require tools for translation services.